With an exaustive test running overnight with the new -mjc branch of 2.4
(I'm working on getting XFS into the branch) I noticed the following
truncating to largest ever: 0x3fcb9
READ BAD DATA: offset = 0x53e5, size = 0x9c0a
OFFSET GOOD BAD RANGE
0x 9000 0x0000 0x0101 0x 5faa
operation# (mod 256) for the bad data may be 1
LOG DUMP (1145 total operations):
I have attached the dump of the results run and the binary difference is
cmp boom boom.fsxgood
boom boom.fsxgood differ: char 10428, line 18
It would be a good idea to use the fsx-linux.c program to stress test XFS.
The fsx-linux program has found several bugs in NFS and other filesystems.