[issue844] fsx on NFS fails

[Thomas Nikolajsen <sinknull@xxxxxxxxxxxxxxxxxxxxxxx>]

Thomas Nikolajsen <thomas.nikolajsen@mail.dk> added the comment:

More details:
fsx params. tried: fsx/dotest and default.

No problems reported by fsx when testing UFS or MFS.

 -thomas
-
fsx/dotest output for NFS-mount dir is:
truncating to largest ever: 0x2abbd1
truncating to largest ever: 0x3abe49
truncating to largest ever: 0x3b1956
truncating to largest ever: 0x3e2816
truncating to largest ever: 0x3e8ae7
READ BAD DATA: offset = 0x124078, size = 0x345ac
OFFSET	GOOD	BAD	RANGE
0x15306e	0x4946	0x4845	0x 55b6
operation# (mod 256) for the bad data may be 72
LOG DUMP (867 total operations):
1(1 mod 256): MAPWRITE 0x2ba358 thru 0x2cc3fb	(0x120a4 bytes)
. .
867(99 mod 256): READ	0x124078 thru 0x158623	(0x345ac bytes)	***RRRR***
Correct content saved for comparison
(maybe hexdump "test.fsx.dat" vs "test.fsx.dat.fsxgood")

-
$ ls -l test.fsx.dat /tmp/test.fsx.dat.fsxgood
-rw-r--r--  1 thomas  wheel   3963049 Nov 22 07:43 /tmp/test.fsx.dat.fsxgood
-rw-r--r--  1 thomas  thomas  3963049 Nov 22 07:43 test.fsx.dat
$ cmp -l test.fsx.dat /tmp/test.fsx.dat.fsxgood | wc -l
   36754
$ cmp -l test.fsx.dat /tmp/test.fsx.dat.fsxgood | head
1388655 110 111
1388656 105 106
1388657 110 111
1388658   1   2
1388659 110 111
1388660 232 233
1388661 110 111
1388662 273 274
1388663 110 111
1388664 161 162

----------
status: unread -> chatting

_____________________________________________________
DragonFly issue tracker <bugs@lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue844>
_____________________________________________________