> We started testing with 2.6.38-rc7 and have seen this bug through to the .0 release. This does not appear to be present in 2.6.33, but we have not done testing in between. We have tested with ext4 and do not encounter this bug. Does reverting commit aea1b9532143218f8599ecedbbd6bfbf812385e1 fix the issue for you?