Nix wrote:
On 19 Sep 2007, maximilian attems said:
i presume it may also be /sys/block/mdNN ?
That's it, e.g. /sys/block/md0. Notable subdirectories include holders/
(block devices within the array, more than one if e.g. LVM is in use),
Also, if you mount the raid as a partitionable one,
NB> Or maybe the drive is failing, but that is badly confusing the
NB> controller, with the same result.
NB> Is it always hde that is reporting errors?
for now - yes; but a few months ago for a short period of time hdg and
hdh also have been reported with errors, but this went away quickly
and n
Linus, please pull from:
git://lost.foo-projects.org/~dwillia2/git/iop async-tx-fixes-for-linus
to receive:
Dan Williams (3):
async_tx: usage documentation and developer notes (v2)
async_tx: fix dma_wait_for_async_tx
raid5: fix 2 bugs in ops_complete_biofill
The raid5
Mr. James W. Laferriere wrote:
Hello Bill & all ,
Bill Davidsen <[EMAIL PROTECTED]> Sat, 22 Sep 2007 09:41:40 -0400 ,
wrote:
My only "advice" is to try and quantify the data volume and look at
nbd vs. iSCSI to provide the mirror if you go that way.
You mentioned nbd as a transport f
On 19 Sep 2007, maximilian attems said:
> hello,
>
> working on initramfs i'd be curious to know what the /sys/block
> entry of a /dev/md/NN device is. have a user request to support
> it and no handy box using it.
>
> i presume it may also be /sys/block/mdNN ?
That's it, e.g. /sys/block/md0. Not
