Re: MDADM 3.3 broken?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 19 Nov 2013 16:35:44 -0800 "David F." <df7729@xxxxxxxxx> wrote:

> FWIW, we confirmed that it appears to be the old RAID1 data it was
> finding - when the partition is below half the size it didn't find it
> in the partition, when resized just beyond half the size (of the RAID0
> md drive), it then started finding it in the partition.
> 
> Also, was Cisco's information useful for why their cisco server (using
> lsi)  RAID5 won't assembly?  Do you think the patch deals with that as
> well?
> 
>

You did say something about Cisco in the original post but it wasn't at all
clear what you were asking or what the context was.

Could you please spell it all out.  You said something about dmraid reporting
something.  Showing the output of dmraid in that case wouldn't hurt.
And show the output of "mdadm --examine /dev/device" for any relevant device
is often a good idea.

NeilBrown

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux