Re: Content Of Files May Be Changed After One Disk Is Failed In RAID5

From: clplayer
Date: Fri Sep 07 2012 - 02:30:49 EST


> --assume-clean is not safe with RAID5 unless the array actually is clean.
> It is safe with RAID1 and RAID6 due to details of the specific implementation.
> So I suspect that is the cause of the corruption.
>
> NeilBrown
>

Thank you for the information.

I have removed --assume-clean in the script and executed the stress
after that raid5 completed resync.

The files are all consistent in the rest tests.

I am now wondering, what's different between the implementation of
raid5 algorithm and of raid6 algorithm?

Would you please suggest some hints in the implementation?

Thank you,
Peng.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/