Re: unsynchronized raid10 with different events count

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

 



On Sat, 31 Jan 2015 17:14:06 +0100 (GMT+01:00) LuVar <luvar@xxxxxxxxxxxx>
wrote:

> Hi,
> finally,
> I have run --re-add thing. It seems that it is what I wanted. My array is now OK.
> 
> So only one question remains. Is there any possibility to make improvements and make array autoassemble if there are clear that in raid10, there is consistent highest events count for at least one drive for raid1 subparts? I have layout=n3 for situations when one drive fails, to be able to correctly recover from others two same copies and to know that given data are probably ok if they are same.

It appears from the mdstat you posted:

Personalities : [raid10] 
md3 : active raid10 sdj[9] sdl[13] sdm[6] sdi[3] sdb[10]
      937709952 blocks super 1.2 128K chunks 3 near-copies [9/5] [U_UU__UU_]
      bitmap: 4/7 pages [16KB], 65536KB chunk

unused devices: <none>


That it *did* autoassemble and provide you with a working array.  It just
didn't include all the devices - because some of them looked old and mdadm
couldn't be sure they were reliable.

You did the correct thing to --re-add them.  That is how you tell mdadm
"these devices are reliable, even though someone went wrong before and they
didn't get updated with the latest event count".

So it appears to me that everything is working correctly.

NeilBrown

Attachment: pgpQoT6lPAVIO.pgp
Description: OpenPGP digital 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