From owner-freebsd-current Wed Jul 19 08:02:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id IAA26523 for current-outgoing; Wed, 19 Jul 1995 08:02:35 -0700 Received: from haywire.DIALix.COM (haywire.DIALix.COM [192.203.228.65]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id IAA26512 for ; Wed, 19 Jul 1995 08:02:27 -0700 Received: (from news@localhost) by haywire.DIALix.COM (8.6.12/8.6.12/DIALix) id XAA03674 for freebsd-current@freebsd.org; Wed, 19 Jul 1995 23:02:16 +0800 Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 19 Jul 1995 23:02:08 +0800 From: peter@haywire.dialix.com (Peter Wemm) Message-ID: <3uj6pg$3h3$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. Subject: what's going on here? (NFSv3 problem?) Sender: current-owner@freebsd.org Precedence: bulk Some time in the last few weeks, doing a ls on a large NFS mounted directory.. It looks like the server is answering with the wrong offset, but it used to work and the server hasn't changed lately (like, years... It's a vintage SVR4.0/386 system.) The freebsd client has it mounted with a read and write size of 1024, which struck me as odd that it appears to be asking for a 8192 byte chunk... It works fine with directory scans of smaller directories.. And yes, I'm just about to run fsirand on the server.. :-) Puzzled, (I don't speak NFS, so please be gentle.. ;-) -Peter jhome # tcpdump -s 10000 -vv port nfs tcpdump: listening on ed0 14:32:00.078577 jhome.f3 > haywire.nfs: 128 lookup fh 0,1/11 "." (ttl 64, id 35407) 14:32:00.083958 haywire.nfs > jhome.f3: reply ok 128 lookup fh 0,1/11 DIR 40755 ids 2004/304 sz 4608 nlink 20 rdev 0 fsid 1 nodeid 122b0 a/m/ctime 806164215.955880 806140879.043601 806140879.043601 (ttl 30, id 56882) 14:32:00.085901 jhome.f4 > haywire.nfs: 128 lookup fh 0,1/11 "." (ttl 64, id 35408) 14:32:00.089350 haywire.nfs > jhome.f4: reply ok 128 lookup fh 0,1/11 DIR 40755 ids 2004/304 sz 4608 nlink 20 rdev 0 fsid 1 nodeid 122b0 a/m/ctime 806164215.955880 806140879.043601 806140879.043601 (ttl 30, id 56883) 14:32:00.090940 jhome.f5 > haywire.nfs: 120 getattr fh 0,1/11 (ttl 64, id 35409) 14:32:00.094075 haywire.nfs > jhome.f5: reply ok 96 getattr DIR 40755 ids 2004/304 sz 4608 (ttl 30, id 56884) [ note that it asks the same thing again ] 14:32:00.095423 jhome.f6 > haywire.nfs: 120 getattr fh 0,1/11 (ttl 64, id 35410) 14:32:00.098540 haywire.nfs > jhome.f6: reply ok 96 getattr DIR 40755 ids 2004/304 sz 4608 (ttl 30, id 56885) [and again.. another getattr...] 14:32:00.099626 jhome.f7 > haywire.nfs: 120 getattr fh 0,1/11 (ttl 64, id 35411) 14:32:00.105959 haywire.nfs > jhome.f7: reply ok 96 getattr DIR 40755 ids 2004/304 sz 4608 (ttl 30, id 56886) [ and here we start the readdir packets.. note the times...] 14:32:00.108383 jhome.f8 > haywire.nfs: 128 readdir fh 0,1/11 8192 bytes @ 0 (ttl 64, id 35412) 14:32:00.120718 haywire.nfs > jhome.f8: reply ok 1472 readdir offset 1 size 74416 eof (frag 56887:1480@0+) (ttl 30) ^^ 14:32:00.315550 jhome.f8 > haywire.nfs: 128 readdir fh 0,1/11 8192 bytes @ 0 (ttl 64, id 35413) 14:32:00.339449 haywire.nfs > jhome.f8: reply ok 1472 readdir offset 1 size 74416 eof (frag 56888:1480@0+) (ttl 30) ^^ 14:32:00.725494 jhome.f8 > haywire.nfs: 128 readdir fh 0,1/11 8192 bytes @ 0 (ttl 64, id 35418) 14:32:00.739364 haywire.nfs > jhome.f8: reply ok 1472 readdir offset 1 size 74416 eof (frag 56889:1480@0+) (ttl 30) ^^ 14:32:01.535204 jhome.f8 > haywire.nfs: 128 readdir fh 0,1/11 8192 bytes @ 0 (ttl 64, id 35420) 14:32:01.547494 haywire.nfs > jhome.f8: reply ok 1472 readdir offset 1 size 74416 eof (frag 56904:1480@0+) (ttl 30) ^^ 14:32:03.144782 jhome.f8 > haywire.nfs: 128 readdir fh 0,1/11 8192 bytes @ 0 (ttl 64, id 35421) 14:32:03.155896 haywire.nfs > jhome.f8: reply ok 1472 readdir offset 1 size 74416 eof (frag 56905:1480@0+) (ttl 30) ^^ 14:32:06.354102 jhome.f8 > haywire.nfs: 128 readdir fh 0,1/11 8192 bytes @ 0 (ttl 64, id 35424) 14:32:06.365342 haywire.nfs > jhome.f8: reply ok 1472 readdir offset 1 size 74416 eof (frag 56907:1480@0+) (ttl 30) ^^ 14:32:12.762514 jhome.f8 > haywire.nfs: 128 readdir fh 0,1/11 8192 bytes @ 0 (ttl 64, id 35426) 14:32:12.775162 haywire.nfs > jhome.f8: reply ok 1472 readdir offset 1 size 74416 eof (frag 56909:1480@0+) (ttl 30) ^^ 14:32:25.569545 jhome.f8 > haywire.nfs: 128 readdir fh 0,1/11 8192 bytes @ 0 (ttl 64, id 35427) 14:32:25.582252 haywire.nfs > jhome.f8: reply ok 1472 readdir offset 1 size 74416 eof (frag 56915:1480@0+) (ttl 30) ^^ 14:32:51.173615 jhome.f8 > haywire.nfs: 128 readdir fh 0,1/11 8192 bytes @ 0 (ttl 64, id 35430) 14:32:51.186349 haywire.nfs > jhome.f8: reply ok 1472 readdir offset 1 size 74416 eof (frag 56922:1480@0+) (ttl 30) ^^ Script done on Wed Jul 19 22:34:54 1995