graid3 data corruption?!?

Ruslan Ermilov ru at FreeBSD.org
Thu Feb 23 13:33:30 PST 2006


On Thu, Feb 23, 2006 at 01:31:16PM +0100, Michael Reifenberger wrote:
> Hi,
> I'm having 5 firewire Disks in one graid3 set.
> and using a fresh STABLE on SMP with an dual AMD64 in i386 mode.
> 
> While doing an md5 checksum of all files in the filesystem
> (~770GB of data) on disk died. graid3 did the right thing
> and disconnected the disk.
> 
> BUT:
> after diffing the md5sums of the files on large file (probably the one
> that got checked during the disk failure) had an different md5sum than 
> before.
> --- md5_11.log  Fri Dec  9 13:23:07 2005
> +++ md5_12.log  Wed Feb 22 18:03:03 2006
> @@ -4460,3 +4460,3 @@
>  MD5 (Backup/totum/root_0_050211_i386.dmp.gz) = 
>  5a3e7b03f48ea4c2cba10624edd996cf
> -MD5 (Backup/totum/root_0_050715.dmp.gz) = 0e154301cbec84571d1df94bf68e3d79
> +MD5 (Backup/totum/root_0_050715.dmp.gz) = 172d7c12b78f3f191c184d467e31a53c
>  MD5 (RIP/.pgp/PGPMacBinaryMappings.txt) = bf1b637a3a69bcbb8d4177be46a1c3ac
> 
> BUT:
> doing a fresh md5sum now in degraded mode of the file I get again
> (the correct) value of:
> MD5 (Backup/totum/root_0_050715.dmp.gz) = 0e154301cbec84571d1df94bf68e3d79
> 
> For me this means, that graid3 gave incorrect data during the disk los.
> This shouldn't happen!
> 
> Any clues how this could happen?
> Has anyone else seen this behaviour?
> 
Yes, we saw it too.  We hope that the last commit to g_raid3.c (in
HEAD) may fix it as well.


Cheers,
-- 
Ruslan Ermilov
ru at FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060223/4dd7ba03/attachment.bin


More information about the freebsd-stable mailing list