On Tue, Jan 22, 2013 at 09:39:02AM -0500, Chris Mason wrote: > On Tue, Jan 22, 2013 at 07:26:15AM -0700, David Sterba wrote: > > On Fri, Jan 04, 2013 at 01:50:59PM +0100, David Sterba wrote: > > > I've noticed a few csum mismatch messages, and a few failed xfstests: > > > > They're still there, we're on rc4, so I started looking for potential > > patches to revert, but tonight the test reproduced csums with these > > patches removed: > > I'm able to trigger crc errors with just 50 parallel fsx O_DIRECT procs > hammering in parallel. Trying to nail down the test case a little > better.
After this patch(Btrfs: put csums on the right ordered extent), I'm unable to get crc errors by running this script. thanks, liubo > > #!/bin/bash > > num=$1 > > if [ "x$num" == "x" ]; then > num=50 > fi > > echo "using $num procs" > > for x in `seq 1 $num` ; do > echo -n "$x " > fsx -q xxxf$x -Z -R -W -r 4096 -w 4096 & > done > echo "waiting" > wait > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
