Re: How to avoid complete rebuild of RAID 6 array (6/8 active devices)

[Neil Brown <neilb@xxxxxxx>]

On Wednesday June 25, maan@xxxxxxxxxxxxxxx wrote:
> On 15:37, Dave Moon wrote:
> 
> > 1. If mdadm encounters a bit error during a RAID 6 rebuild, will it  
> > just give up on that particular file and move on to recover other data  
> > on the array? Or will it trash the entire array?
> 
> The kernel will stop the array and give up.

Not quite.  It will stop the recovery.  It won't stop the whole array
though (I think...).

> 
> > 2. Is it possible to cheat mdadm by somehow replacing the new "raid  
> > metadata" on the 6 drives with the old data on the 2 drives? Will it  
> > make mdadm think the array is clean, consistent and nothing ever  
> > happened?
> 
> > Please do note that I did not write ANY new data onto the RAID 6 array  
> > from the time it was degraded until the time I brought it down with (-- 
> > stop).
> 
> Use --force, Luke. Man mdadm(8):
> 
> 	-f, --force Assemble the array even if some superblocks
> 	appear out-of-date

--force only updates enough superblocks to assemble a working array.
For raid6, that mean n-2 drives.  As there are n-2 drive, it won't try
any harder.

You best bet is to recreate the array with --assume-clean.
Providing you have the chunksize, order of devices, etc the same, you
should get your array back.

NeilBrown
--
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