On 5/25/20 5:23 PM, Patrick O'Callaghan wrote:
Yes, I understand that. I still think the behaviour of mdadm in this
case is counter-intuitive. When I explicitly ask for the creation of an
array called /dev/md0 and the command first of all warns me that this
will (not "may") destroy the existing partition table and do I want to
proceed, then when I say yes apparently succeeds, I think I'm entitled
to think that /dev/md0 has been created, but it hasn't.
remember /dev is created at linux boot so the devices names are dynamic
(/dev/mdN)
if you want give a name to the array and a device name under /dev/md
something like:
mdadm --create /dev/md/var-even --raid-devices=2 --level=1
--name=var-even /dev/sd[ab]12
the above command uses partition number 12 type fd00 on /dev/sd[ab]
and format with:
mkfs.ext4 -L 'var-even' /dev/md/var-even
to prevent name collisions (if you mount the disk in another computer
with identical setup) find the partition uuid with:
ls -lht /dev/md/var-even
lrwxrwxrwx. 1 root root 8 May 20 21:48 /dev/md/var-even -> ../md121
and find the uuid pointing to md121 with:
ls -lht /dev/disk/by-uuid/
...
lrwxrwxrwx. 1 root root 11 May 20 21:48
2108ba12-2ee3-5067-8de4-01c454867c5a -> ../../md121
...
and use that uuid in fstab.
Gabriel
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
