Raid has been in quite a shocking state for a long while and
often there seems nor rhyme nor reason to its behaviour. If you want
to stick your machine in an endless loop, just try initialising a
mirror raid device with only one of its two components currently
> are rejected with "/dev/md0: Device or resource busy". Even shutting
ya, ya. Try raidhotsetfaulty for good luck and then try raidhotremove.
(curse, splutter. Will the authors ever write some docs that make
sense. And also document the interactions with lvm).
> down to single user mode does not release the device for stopping. I
> had to reboot to single user mode, then I was able to stop it,
You just said you couldn't?
> unconfigure it, etc.
> Testing the throughput of Linux's software raid in levels raid1 and
> raid0 with various chunksizes was somewhat more tedious because of this
You ain't kidding. It's a nightmare to test upon.
> Here is my (current) raidtab:
> Raiddev /dev/md0
> raid-level 0
> nr-raid-disks 2
> chunk-size 64k
> persistent-superblock 1
> nr-spare-disks 0
> device /dev/sda2
> raid-disk 0
> device /dev/sdb1
> raid-disk 1
That's a standard setup. It's not even confusing to me! Try it over lvm
logical partitions and other raid devices (snicker).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/