man raidtab says
failed-disk index
The most recently defined device is inserted at position index in
the raid array as a failed device. This allows you to create raid
1/4/5 devices in degraded mode - useful for installation. Don't
use
Iain,
On Wed, 20 Jun 2001, Iain Campbell wrote:
man raidtab says
failed-disk index
The most recently defined device is inserted at position index in
the raid array as a failed device. This allows you to create raid
1/4/5 devices in degraded mode - useful for
Linus,
it is possible to start an md array from the boot command line with,
e.g.
md=0,/dev/something,/dev/somethingelse
However only names recognised by name_to_kdev_t work here. devfs
based names do not work.
To fix this, the follow patch moves the name lookup from __setup
Linus,
This patch makes sure that all the printks in md.c print a message
starting with md: or md%d:.
The next step (not today) will be to reduce a lot of them to
KERN_INFO or similar as md is really quite noisy.
Also, two printks in raid1.c get prefixed with raid1:
This patch is
Linus, and fellow RAIDers,
This is the third in my three patch series for improving RAID5
throughput.
This one substantially lifts write thoughput by leveraging the
opportunities for write gathering provided by the first patch.
With RAID5, it is much more efficient to write a whole
Linus,
There is a buggy BUG in the raid5 code.
If a request on an underlying device reports an error, raid5 finds out
which device that was and marks it as failed. This is fine.
If another request on the same device reports an error, raid5 fails
to find that device in its table (because
