On 20/02/2015 01:23, Mikael Abrahamsson wrote:
On Thu, 19 Feb 2015, John Andre Taule wrote:
I'm a bit surprised that overwriting anything on the physical disk
should corrupt the file system on the raid. I would think that would
be similar to a disk crashing or failing in other ways.
Errr, in raid5 you have data blocks and parity blocks. WHen you
overwrite one of the component drives with zeroes, you're effectively
doing the same as writing 0:es to a non-raid drive every 3
$stripesize. You're zero:ing a lot of the filesystem information.
What you say that Linux might not have seen the disk as failing is
interesting. This could explain why the file system got corrupted.
Correct. There is no mechanism that periodically checks the contents
of the superblock and fails the drive if it's not there anymore. So
the drive is never failed.
In addition, there is no checking of the data when read to confirm that
the data on the first 4 disks = the checksum on the 5th disk (assuming a
5 disk raid5). This applies equally to all raid levels as currently
working from linux md raid. While there are some use cases where it
would be nice to confirm that the data read is correct, this has not yet
been implemented (for live operation, you can schedule a check at
periodic intervals).
Even if MD noticed that the value of the first 4 disks did not equal the
checksum on the 5th disk, it has no method to determine which disk
contained the wrong value (could be any of the data stripes, or the
parity stripe). raid6 begins to allow for this type of check, and I
remember a lot of work being done on this, however, I think that was
still an offline tool more useful for data recovery from partially
failed multiple drives.
From memory, there are filesystems which will do what you are asking
(check that the data received from disk is correct, use multiple 'disks'
and ensure protection from x failed drives, etc. I am certain zfs and
btrfs both support this. (I've never used either due to stability
concerns, but I read about them every now and then....)
Regards,
Adam
--
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
