Question about a mismatch between documentation and how mdadm currently works.
Kevin O'Gorman
kogorman at gmail.com
Sun Apr 2 01:50:22 UTC 2017
I'm fooling around with RAID on Linux for the first time. Lots to learn.
I have one issue that
keeps coming up with creating RAID arrays with mdadm.
The documentation I have all says to create arrays with something like
mdadm --create /dev/md0 (and some more stuff)
and what follows really does indicate they expect the array to appear as
/dev/md0. What
happens when I try it is that the array is created as /dev/md127. If I
create two arrays, the
next one is /dev/md126.
Likewise, if I assemble a RAID array, they go to the high numbers no matter
what my command-line says.
What's up with this? Is it historical? Is something just ignoring that
part of the command line? Is that part even required?
++ kevindf
--
Kevin O'Gorman
#define QUESTION ((bb) || (!bb)) /* Shakespeare */
Please consider the environment before printing this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20170401/1d6a1d53/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 441 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20170401/1d6a1d53/attachment.gif>
More information about the ubuntu-users
mailing list