Re: and again: broken RAID5

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

 



On 10/05/2012 11:45, NeilBrown wrote:
On Thu, 10 May 2012 11:19:30 +0100 John Robinson
<john.robinson@xxxxxxxxxxxxxxxx>  wrote:

On 10/05/2012 10:20, NeilBrown wrote:
[...]
Just add --force the to --assemble command.

I think I'd assemble from only 3 drives, sdh, sdf and sdj, because sdi's
event count is so much lower it must be the one that was knocked out
first and you probably want to resync onto it (or a fresh drive if it's
actually faulty).

correct.  And that is exactly what "mdadm --assemble --force" will decide
too. :-)
It will assemble from h, f, j and exclude i.

Ah - I didn't know it was clever enough to do that, I had assumed that if you forced all the drives they'd all be marked up-to-date.

What should I do if I had 3 different event counts (like this case) all fairly close to each other (unlike this case) and I really did want to force them all, avoiding a resync?

Cheers,

John.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[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