Re: [PATCH] Btrfs: put csums on the right ordered extent

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

 



On Wed, Jan 23, 2013 at 08:21:07AM -0700, David Sterba wrote:
> On Wed, Jan 23, 2013 at 12:01:08PM +0100, David Sterba wrote:
> > Survived a few hours of Chris' test and I'm running the full xfstests
> > again now.
> 
> After 4.5 hours of the same testsuite as before, this popped up in
> syslog:
> 
> [53489.998888] btrfs csum failed ino 63793 off 106496 csum 2411266714 private 3462448526
> 
> the file is $TEST/junk . Running md5sum on that file produces a
> different checksum error messages:
> 
> [54187.259285] btrfs csum failed ino 63793 off 344064 csum 2566472073 private 1022717503
> (3 times)
> 
> I've rerun chris' script again, no errors, and rechecked if I'm running
> the kernel, yes.

Looks like Josef saw the same, so we have two different bugs (missing
crcs vs incorrect crcs).  Josef mentioned a much faster test for the
incorrect crcs...Josef what was that test?

Thanks to everyone that ran my script, sorry it ended up a distraction.

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


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux