* md has hard coded maximum number of drives?
@ 2008-11-04 21:21 Gregory Stark
0 siblings, 0 replies; 2+ messages in thread
From: Gregory Stark @ 2008-11-04 21:21 UTC (permalink / raw)
To: linux-raid
Ah, nevermind. I just discovered that mdadm defaults to the old 0.90 format
superblock. I suppose that's still a WTF but at least it makes sense.
Perhaps the error message should explain exactly *why* 28+ is invalid and
suggest using -e to work around the problem.
--
greg
^ permalink raw reply [flat|nested] 2+ messages in thread
* md has hard coded maximum number of drives?
@ 2008-11-04 20:26 Gregory Stark
0 siblings, 0 replies; 2+ messages in thread
From: Gregory Stark @ 2008-11-04 20:26 UTC (permalink / raw)
To: linux-raid
# mdadm --create /dev/md0 --level 0 --raid-devices 60 `cat drives`
mdadm: invalid number of raid devices: 60
# mdadm --create /dev/md0 --level 0 --raid-devices 32 `cat drives`
mdadm: invalid number of raid devices: 32
# mdadm --create /dev/md0 --level 0 --raid-devices 33 `cat drives`
mdadm: invalid number of raid devices: 33
Firstly, "invalid number" is a terrible error message. 60 is a perfectly good
number. The error message gives no indication of why it doesn't find 60 to be
a "valid" number.
Secondly there's no mention in any documentation for mdadm or anywhere else
that I can find of any arbitrary maximum number of drives.
Thirdly, WTF?!
--
greg
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-11-04 21:21 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-04 21:21 md has hard coded maximum number of drives? Gregory Stark
-- strict thread matches above, loose matches on Subject: below --
2008-11-04 20:26 Gregory Stark
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).