From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.5.60 NFS FSX
Date: Thu, 13 Feb 2003 15:27:42 +0000 [thread overview]
Message-ID: <20030213152742.GA1560@codemonkey.org.uk> (raw)
2.5.60's NFS seems to have various issues.
(2.5.60 client, 2.4.21pre3 server)
- I ran an fsx and an fsstress in parallel.
Client rebooted after 2-3 minutes.
- fsx on its own, after quite a while, this happens..
truncating to largest ever: 0x3ffff
skipping zero size read
skipping zero size write
skipping zero size write
skipping zero size write
READ BAD DATA: offset = 0x358ba, size = 0x4867
OFFSET GOOD BAD RANGE
0x36000 0x0000 0x8c1a 0x 1ff3
operation# (mod 256) for the bad data may be 140
LOG DUMP (176283 total operations):
176284(156 mod 256): READ 0x35b07 thru 0x38c67 (0x3161 bytes) ***RRRR***
176285(157 mod 256): READ 0x12552 thru 0x1af77 (0x8a26 bytes)
176286(158 mod 256): WRITE 0x3560f thru 0x3ffff (0xa9f1 bytes) ***WWWW
176287(159 mod 256): MAPWRITE 0x1aaae thru 0x233bf (0x8912 bytes)
176288(160 mod 256): MAPREAD 0x3635d thru 0x3661b (0x2bf bytes)
176289(161 mod 256): MAPREAD 0x374c0 thru 0x3ba42 (0x4583 bytes) ***RRRR***
176290(162 mod 256): WRITE 0x16794 thru 0x192eb (0x2b58 bytes)
176291(163 mod 256): READ 0x128bf thru 0x1d5b0 (0xacf2 bytes)
176292(164 mod 256): READ 0x330d5 thru 0x35b26 (0x2a52 bytes)
176293(165 mod 256): MAPREAD 0xff6b thru 0x13c4e (0x3ce4 bytes)
176294(166 mod 256): MAPWRITE 0x1c5e0 thru 0x2a720 (0xe141 bytes)
176295(167 mod 256): MAPWRITE 0x2a8df thru 0x2e628 (0x3d4a bytes)
176296(168 mod 256): MAPWRITE 0x370cc thru 0x3be24 (0x4d59 bytes) ******WWWW
176297(169 mod 256): MAPWRITE 0x21637 thru 0x30999 (0xf363 bytes)
... <much more spew ..
(full log is at http://www.codemonkey.org.uk/cruft/nfs-fsx-2.5.60.txt )
Finally, I see a lot of these in the client logs..
NFS: server cheating in read reply: count 8192 > recvd 1000
NFS: server cheating in read reply: count 8192 > recvd 1000
NFS: server cheating in read reply: count 8192 > recvd 1000
NFS: server cheating in read reply: count 3888 > recvd 1000
NFS: server cheating in read reply: count 8192 > recvd 1000
NFS: server cheating in read reply: count 8192 > recvd 1000
...
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next reply other threads:[~2003-02-13 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 15:27 Dave Jones [this message]
2003-02-13 15:45 ` 2.5.60 NFS FSX Trond Myklebust
2003-02-13 15:51 ` Dave Jones
2003-02-13 16:04 ` Trond Myklebust
2003-02-13 16:05 ` Dave Jones
2003-02-13 18:54 ` Joel Becker
2003-02-13 19:08 ` Trond Myklebust
2003-02-13 19:27 ` Dave Jones
[not found] ` <20030213204906.GA24109@codemonkey.org.uk>
2003-02-13 21:12 ` Trond Myklebust
2003-02-13 21:30 ` Dave Jones
2003-02-13 22:05 ` Dave Jones
2003-02-13 22:15 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030213152742.GA1560@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.