change expected result to fail (0 -> 1) as trying to execute chattr on a barrier from context 2 is expected to fail. this test is problematic because some versions of chattr (e2fsprogs 1.40.8-2ubuntu2 in ubuntu hardy) return success even though the barrier is not visible to chattr (ie "chattr: No such file or directory while trying to stat "). so even though chattr failed to act on the barrier (as it could not see it), it still reports success (ie exit code 0). todo/suggestion: first stat the barrier and only try to chattr the barrier if stat is successful (because if stat fails, then chattr will definitely fail). --- /root/bin/testfs.sh-0.20a 2009-08-19 10:02:33.000000000 -0500 +++ /root/bin/testfs.sh-0.20b 2009-08-19 12:04:09.000000000 -0500 @@ -494,7 +494,7 @@ function do_test () { eexec 102 0 "setattr --barrier $dpath" eexec 103 0 "do_xattr_verify $MNT showattr $dpath $attr_B" eexec 104 0 "do_xattr_verify $MNT lsattr $dpath $lsattr_B" - eexec 105 0 "go_xid 2 chattr =i $dpath" + eexec 105 1 "go_xid 2 chattr =i $dpath" eexec 106 0 "do_xattr_barrier $MNT $dpath ..^" eexec 108 0 "setattr --~barrier $dpath" eexec 109 0 "do_xattr_verify $MNT showattr $dpath $attr_b"