All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: stale nfs file handle with exported loopback mounts
@ 2007-10-31 22:50 devzero
  2007-11-01  4:26 ` Neil Brown
  0 siblings, 1 reply; 17+ messages in thread
From: devzero @ 2007-10-31 22:50 UTC (permalink / raw)
  To: J. Bruce Fields; +Cc: Neil Brown, NFS

ok, i just wanted to tell that this isn`t the right way to go imho.

some time ago i have tested exporting a parent dir containing several loopb=
ack mounted iso images with some pre-1.1.0 nfs-utils version and it worked =
- so =EC wonder why it now seems to have issues as things should have gone =
stable.....




> -----Urspr=FCngliche Nachricht-----
> Von: "J. Bruce Fields" <bfields@fieldses.org>
> Gesendet: 31.10.07 23:39:46
> An: devzero@web.de
> CC: NFS@lists.sourceforge.net, Neil Brown <neilb@suse.de>
> Betreff: Re: [NFS] stale nfs file handle with exported loopback mounts


> =

> On Wed, Oct 31, 2007 at 11:19:43PM +0100, devzero@web.de wrote:
> > >If you add an explicit export for each one, =

> > you mean, i should export each of those ~500 loopback mounted iso image=
s ?
> > come on, that`s not what admins or users want, isn`t it ?
> =

> No, of course not; I was just suggesting it as a way to confirm that's
> where the problem is.
> =

> --b.
> =

> > =

> > > -----Urspr=FCngliche Nachricht-----
> > > Von: "J. Bruce Fields" <bfields@fieldses.org>
> > > Gesendet: 31.10.07 21:58:00
> > > An: devzero@web.de
> > > CC: Neil Brown <neilb@suse.de>, NFS@lists.sourceforge.net
> > > Betreff: Re: [NFS] stale nfs file handle with exported loopback mounts
> > =

> > =

> > > =

> > > On Wed, Oct 31, 2007 at 09:46:13PM +0100, devzero@web.de wrote:
> > > > hi !
> > > > =

> > > > i tried latest grml build (lenny/sid) as server today (suse 9.3 as =
client).
> > > > =

> > > > error still existing, but a little bit different:
> > > > =

> > > > if i cd to the loopback-mount dir`s on the client, i see the conten=
ts of the parent directory, i.e. i get a recursion.
> > > =

> > > That suggests something funky in the way we're identifying those
> > > filesystems in the filehandle.  If you add an explicit export for each
> > > one, each with its own "fsid=3Dxyz" option (with xyz whatever positive
> > > integer you'd like, as long as it's difficult for export), does the
> > > problem go away??
> > > =

> > > --b.
> > > =

> > > > =

> > > > regards
> > > > roland
> > > > =

> > > > =

> > > > =

> > > > > -----Urspr=FCngliche Nachricht-----
> > > > > Von: devzero@web.de
> > > > > Gesendet: 30.10.07 21:05:56
> > > > > An: Neil Brown <neilb@suse.de>
> > > > > CC: NFS@lists.sourceforge.net
> > > > > Betreff: Re: [NFS] stale nfs file handle with exported loopback m=
ounts
> > > > =

> > > > =

> > > > > =

> > > > > > I recommend replacing subtree_check with no_subtree_check, but =
it
> > > > > > shouldn't make an important difference in this case.
> > > > > =

> > > > > ok, i leave it as is.
> > > > > =

> > > > > > This should work with nfs-utils 1.1.0 or later.  With earlier r=
eleases
> > > > > > you need to explicitly export the subordinate filesystems too.
> > > > > > =

> > > > > =

> > > > > mhh - opensuse doesn`t have nfs-utils package, but it has nfs-cli=
ent-1.1.0-8 which looks like they repackaged nfs-utils 1.1.0
> > > > > =

> > > > > > It is a little odd that the errors are inconsistent.
> > > > > =

> > > > > ok, but only a minor issue, if an issue at all, isn`t it ?
> > > > > =

> > > > > > Can you find any log messages from mountd in syslog?  What do t=
hey
> > > > > > say?
> > > > > =

> > > > > yes, on the client i`m getting :
> > > > > =

> > > > > Jun  3 21:36:01 linux kernel: nfs_update_inode: inode number mism=
atch
> > > > > Jun  3 21:36:01 linux kernel: expected (0:11/0x2), got (0:11/0x13=
881)
> > > > > Jun  3 21:36:01 linux kernel: nfs_update_inode: inode number mism=
atch
> > > > > Jun  3 21:36:01 linux kernel: expected (0:11/0x2), got (0:11/0x13=
881)
> > > > > Jun  3 21:36:17 linux kernel: nfs_update_inode: inode number mism=
atch
> > > > > Jun  3 21:36:17 linux kernel: expected (0:11/0x2), got (0:11/0x13=
881)
> > > > > Jun  3 21:36:17 linux kernel: nfs_update_inode: inode number mism=
atch
> > > > > Jun  3 21:36:17 linux kernel: expected (0:11/0x2), got (0:11/0x13=
881)
> > > > > Jun  3 21:36:20 linux kernel: nfs_update_inode: inode number mism=
atch
> > > > > Jun  3 21:36:20 linux kernel: expected (0:11/0x2), got (0:11/0x13=
881)
> > > > > Jun  3 21:36:20 linux kernel: nfs_update_inode: inode number mism=
atch
> > > > > =

> > > > > =

> > > > > no error message on the server:
> > > > > Oct 26 10:09:31 opensuse103 mountd[4293]: authenticated unmount r=
equest from 10.0.0.40:1014 for /mnt (/mnt)
> > > > > Oct 26 10:10:07 opensuse103 mountd[4293]: authenticated mount req=
uest from 10.0.0.40:612 for /mnt (/mnt)
> > > > > Oct 26 10:10:43 opensuse103 mountd[4293]: authenticated unmount r=
equest from 10.0.0.40:623 for /mnt (/mnt)
> > > > > Oct 26 10:10:52 opensuse103 mountd[4293]: authenticated mount req=
uest from 10.0.0.40:624 for /mnt (/mnt)
> > > > > =

> > > > > > Also what does
> > > > > >    cat /proc/fs/nfsd/exports
> > > > > > =

> > > > > > on the server show.
> > > > > =

> > > > > opensuse103:~ # cat /proc/fs/nfsd/exports
> > > > > # Version 1.1
> > > > > # Path Client(Flags) # IPs
> > > > > /mnt/iso1       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D2=
c49fef2:ba464293:9b2bf2b8:322ccbcb)
> > > > > /mnt/iso3       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D2=
7ae9c67:0b794b36:8b5e9e17:37b569eb)
> > > > > /mnt    *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D08164ee4:=
2db141eb:ac961701:49c74396)
> > > > > /mnt/iso2       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D2=
aad6ea5:a05d4441:b94c48e6:e5d9981e)
> > > > > =

> > > > > =

> > > > > > Finally, a tcpdump:
> > > > > > =

> > > > > >   tcpdump -s 0 -w /tmp/tcpdump port 2049
> > > > > > =

> > > > > > while you run the experiment might help.
> > > > > =

> > > > > ah - this seems to give a hint, but i don`t have a clue why the s=
erver (10.0.0.30) is telling the client (10.0.0.40) a "RPC Version mismatch=
".
> > > > > I also tried  --no-nfs-version 4 for rpc.mountd (setting in /etc/=
sysconfig/nfs), but this didn`t make a difference.
> > > > > =

> > > > > here is the tcpdump output - i did =

> > > > > =

> > > > > - mount
> > > > > - ls / ls -la / cd to subdirs
> > > > > =

> > > > > 10:15:06.480542 IP 10.0.0.40.0 > 10.0.0.30.2049: 0 null
> > > > > 10:15:06.480572 IP 10.0.0.30.2049 > 10.0.0.40.0: reply ERR 0: RPC=
 Version mismatch (167772160-0)
> > > > > 10:15:06.480765 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 2031114=
913 win 1460 <nop,nop,timestamp 686128 737918>
> > > > > 10:15:06.480821 IP 10.0.0.40.2079804678 > 10.0.0.30.2049: 108 fsi=
nfo fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743963CD8=
1908
> > > > > 10:15:06.480833 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 108 win=
 181 <nop,nop,timestamp 737918 686128>
> > > > > 10:15:06.513365 IP 10.0.0.30.2049 > 10.0.0.40.2079804678: reply o=
k 84 fsinfo rtmax 65536 rtpref 65536 wtmax 65536 wtpref 65536 dtpref 4096
> > > > > 10:15:06.514408 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 85 win =
1460 <nop,nop,timestamp 686160 737926>
> > > > > 10:15:06.514902 IP 10.0.0.40.2096581894 > 10.0.0.30.2049: 108 get=
attr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743963CD=
81908
> > > > > 10:15:06.515256 IP 10.0.0.30.2049 > 10.0.0.40.2096581894: reply o=
k 116 getattr DIR 40755 ids 0/0 sz 4096
> > > > > 10:15:06.553865 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 201 win=
 1460 <nop,nop,timestamp 686201 737926>
> > > > > 10:16:03.091784 IP 10.0.0.40.2113359110 > 10.0.0.30.2049: 108 get=
attr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C74396472=
19C8C
> > > > > 10:16:03.093366 IP 10.0.0.30.2049 > 10.0.0.40.2113359110: reply o=
k 116 getattr DIR 40755 ids 0/0 sz 4096
> > > > > 10:16:03.096046 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 317 win=
 1460 <nop,nop,timestamp 743610 752071>
> > > > > 10:16:03.097370 IP 10.0.0.40.2130136326 > 10.0.0.30.2049: 112 acc=
ess fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
001F 001f
> > > > > 10:16:03.098156 IP 10.0.0.30.2049 > 10.0.0.40.2130136326: reply o=
k 124 access c 0003
> > > > > 10:16:03.156812 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 441 win=
 1460 <nop,nop,timestamp 743651 752072>
> > > > > 10:16:08.967804 IP 10.0.0.40.2146913542 > 10.0.0.30.2049: 108 get=
attr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C74396000=
00000
> > > > > 10:16:08.968305 IP 10.0.0.30.2049 > 10.0.0.40.2146913542: reply o=
k 116 getattr DIR 40755 ids 0/0 sz 4096
> > > > > 10:16:08.974285 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 557 win=
 1460 <nop,nop,timestamp 749477 753540>
> > > > > 10:16:08.975739 IP 10.0.0.40.2163690758 > 10.0.0.30.2049: 132 rea=
ddirplus fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439=
600000000 512 bytes @ 0
> > > > > 10:16:08.975985 IP 10.0.0.30.2049 > 10.0.0.40.2163690758: reply o=
k 1448 readdirplus
> > > > > 10:16:08.976510 IP 10.0.0.30.2049 > 10.0.0.40.1684108288: reply U=
nknown rpc response code=3D2021855861 340
> > > > > 10:16:08.982238 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 2345 wi=
n 2184 <nop,nop,timestamp 749479 753541>
> > > > > 10:16:08.984415 IP 10.0.0.40.2180467974 > 10.0.0.30.2049: 116 loo=
kup fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
0004 "iso3"
> > > > > 10:16:08.984931 IP 10.0.0.30.2049 > 10.0.0.40.2180467974: reply o=
k 232 lookup fh Unknown/0100060027AE9C670B794B368B5E9E1737B569EB00000001000=
00002000041ED
> > > > > 10:16:09.008819 IP 10.0.0.40.2197245190 > 10.0.0.30.2049: 104 get=
attr fh Unknown/0100060027AE9C670B794B368B5E9E1737B569EB0000000FDD22CC3C700=
2F0AC
> > > > > 10:16:09.010946 IP 10.0.0.30.2049 > 10.0.0.40.2197245190: reply o=
k 188 getattr REG 2 ids 5/0 sz 0
> > > > > 10:16:09.032541 IP 10.0.0.40.2214022406 > 10.0.0.30.2049: 128 get=
attr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E66=
D0700
> > > > > 10:16:09.033405 IP 10.0.0.30.2049 > 10.0.0.40.2214022406: reply o=
k 188 getattr REG 1 ids 1/0 sz 0
> > > > > 10:16:09.033490 IP 10.0.0.40.2230799622 > 10.0.0.30.2049: 128 get=
attr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E56=
D0700
> > > > > 10:16:09.036811 IP 10.0.0.30.2049 > 10.0.0.40.2230799622: reply o=
k 188 getattr REG 1 ids 1/0 sz 0
> > > > > 10:16:09.037823 IP 10.0.0.40.2247576838 > 10.0.0.30.2049: 108 get=
attr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C74396000=
00000
> > > > > 10:16:09.039817 IP 10.0.0.30.2049 > 10.0.0.40.2247576838: reply o=
k 116 getattr DIR 40755 ids 0/0 sz 4096
> > > > > 10:16:09.040423 IP 10.0.0.40.2264354054 > 10.0.0.30.2049: 112 get=
attr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C74396000=
0000F
> > > > > 10:16:09.040856 IP 10.0.0.30.2049 > 10.0.0.40.2264354054: reply o=
k 188 getattr REG 2 ids 5/0 sz 0
> > > > > 10:16:09.041590 IP 10.0.0.40.2281131270 > 10.0.0.30.2049: 116 loo=
kup fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
0004 "iso2"
> > > > > 10:16:09.041920 IP 10.0.0.30.2049 > 10.0.0.40.2281131270: reply o=
k 232 lookup fh Unknown/010006002AAD6EA5A05D4441B94C48E6E5D9981E00000001000=
00002000041ED
> > > > > 10:16:09.049633 IP 10.0.0.40.2297908486 > 10.0.0.30.2049: 104 get=
attr fh Unknown/010006002AAD6EA5A05D4441B94C48E6E5D9981E0000000F5FDC8445432=
6E193
> > > > > 10:16:09.049781 IP 10.0.0.30.2049 > 10.0.0.40.2297908486: reply o=
k 188 getattr REG 2 ids 5/0 sz 0
> > > > > 10:16:09.063218 IP 10.0.0.40.2314685702 > 10.0.0.30.2049: 128 get=
attr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E46=
D0700
> > > > > 10:16:09.072505 IP 10.0.0.30.2049 > 10.0.0.40.2314685702: reply o=
k 188 getattr REG 1 ids 1/0 sz 0
> > > > > 10:16:09.091698 IP 10.0.0.40.2331462918 > 10.0.0.30.2049: 124 get=
attr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E46=
D0700
> > > > > 10:16:09.092022 IP 10.0.0.30.2049 > 10.0.0.40.2331462918: reply o=
k 116 getattr REG 100644 ids 0/0 sz 1048576
> > > > > 10:16:09.128971 IP 10.0.0.40.2348240134 > 10.0.0.30.2049: 128 get=
attr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E36=
D0700
> > > > > 10:16:09.129304 IP 10.0.0.30.2049 > 10.0.0.40.2348240134: reply o=
k 188 getattr REG 1 ids 1/0 sz 0
> > > > > 10:16:09.184155 IP 10.0.0.40.2365017350 > 10.0.0.30.2049: 124 get=
attr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E36=
D0700
> > > > > 10:16:09.184582 IP 10.0.0.30.2049 > 10.0.0.40.2365017350: reply o=
k 116 getattr REG 100644 ids 0/0 sz 1048576
> > > > > 10:16:09.189234 IP 10.0.0.40.2381794566 > 10.0.0.30.2049: 116 loo=
kup fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
0004 "iso1"
> > > > > 10:16:09.189435 IP 10.0.0.30.2049 > 10.0.0.40.2381794566: reply o=
k 232 lookup fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB00000001000=
00002000041ED
> > > > > 10:16:09.193476 IP 10.0.0.40.2398571782 > 10.0.0.30.2049: 104 get=
attr fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000F58896A884A0=
C62B7
> > > > > 10:16:09.193652 IP 10.0.0.30.2049 > 10.0.0.40.2398571782: reply o=
k 188 getattr REG 2 ids 5/0 sz 0
> > > > > 10:16:09.194937 IP 10.0.0.40.2415348998 > 10.0.0.30.2049: 128 get=
attr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E76=
D0700
> > > > > 10:16:09.195033 IP 10.0.0.30.2049 > 10.0.0.40.2415348998: reply o=
k 188 getattr REG 1 ids 1/0 sz 0
> > > > > 10:16:09.195230 IP 10.0.0.40.2432126214 > 10.0.0.30.2049: 128 get=
attr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E86=
D0700
> > > > > 10:16:09.323635 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 2572 wi=
n 416 <nop,nop,timestamp 753629 749566>
> > > > > 10:16:09.324345 IP 10.0.0.30.2049 > 10.0.0.40.2432126214: reply o=
k 188 getattr REG 1 ids 1/0 sz 0
> > > > > 10:16:09.341475 IP 10.0.0.40.2448903430 > 10.0.0.30.2049: 128 get=
attr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E26=
D0700
> > > > > 10:16:09.341524 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 2700 wi=
n 449 <nop,nop,timestamp 753632 749707>
> > > > > 10:16:09.341928 IP 10.0.0.30.2049 > 10.0.0.40.2448903430: reply o=
k 188 getattr REG 1 ids 1/0 sz 0
> > > > > 10:16:09.342117 IP 10.0.0.40.2465680646 > 10.0.0.30.2049: 124 get=
attr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E26=
D0700
> > > > > 10:16:09.343404 IP 10.0.0.30.2049 > 10.0.0.40.2465680646: reply o=
k 116 getattr REG 100644 ids 0/0 sz 1048576
> > > > > 10:16:09.389316 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 5573 wi=
n 2184 <nop,nop,timestamp 749751 753633>
> > > > > 10:16:13.449513 IP 10.0.0.40.2482457862 > 10.0.0.30.2049: 108 get=
attr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C74396472=
19CB5
> > > > > 10:16:13.449815 IP 10.0.0.30.2049 > 10.0.0.40.2482457862: reply o=
k 116 getattr DIR 40755 ids 0/0 sz 4096
> > > > > 10:16:13.452344 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 5689 wi=
n 2184 <nop,nop,timestamp 753943 754660>
> > > > > 10:16:13.453973 IP 10.0.0.40.2499235078 > 10.0.0.30.2049: 100 get=
attr fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB47219C8C00000000472=
19C8C
> > > > > 10:16:13.454154 IP 10.0.0.30.2049 > 10.0.0.40.2499235078: reply o=
k 116 getattr DIR 40755 ids 0/0 sz 4096
> > > > > 10:16:13.456194 IP 10.0.0.40.2516012294 > 10.0.0.30.2049: 108 get=
attr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C74396472=
19C8C
> > > > > 10:16:13.456361 IP 10.0.0.30.2049 > 10.0.0.40.2516012294: reply o=
k 116 getattr DIR 40755 ids 0/0 sz 4096
> > > > > 10:16:13.458282 IP 10.0.0.40.2532789510 > 10.0.0.30.2049: 116 loo=
kup fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
0004 "iso1"
> > > > > 10:16:13.458461 IP 10.0.0.30.2049 > 10.0.0.40.2532789510: reply o=
k 232 lookup fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB00000001000=
00002000041ED
> > > > > 10:16:13.510637 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 6153 wi=
n 2184 <nop,nop,timestamp 753985 754662>
> > > > > 10:16:14.030110 IP 10.0.0.40.2549566726 > 10.0.0.30.2049: 112 acc=
ess fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
001F 001f
> > > > > 10:16:14.030927 IP 10.0.0.30.2049 > 10.0.0.40.2549566726: reply o=
k 124 access c 0003
> > > > > 10:16:14.033436 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 6277 wi=
n 2184 <nop,nop,timestamp 754548 754805>
> > > > > 10:16:14.034732 IP 10.0.0.40.2566343942 > 10.0.0.30.2049: 108 get=
attr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C74396000=
00000
> > > > > 10:16:14.034980 IP 10.0.0.30.2049 > 10.0.0.40.2566343942: reply o=
k 116 getattr DIR 40755 ids 0/0 sz 4096
> > > > > 10:16:14.037319 IP 10.0.0.40.2583121158 > 10.0.0.30.2049: 112 acc=
ess fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
001F 001f
> > > > > 10:16:14.037486 IP 10.0.0.30.2049 > 10.0.0.40.2583121158: reply o=
k 124 access c 0003
> > > > > 10:16:14.040323 IP 10.0.0.40.2599898374 > 10.0.0.30.2049: 132 rea=
ddirplus fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439=
600000000 512 bytes @ 0
> > > > > 10:16:14.040554 IP 10.0.0.30.2049 > 10.0.0.40.2599898374: reply o=
k 1448 readdirplus
> > > > > 10:16:14.041020 IP 10.0.0.30.2049 > 10.0.0.40.1684108288: reply U=
nknown rpc response code=3D2021855861 340
> > > > > 10:16:14.043583 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8305 wi=
n 2908 <nop,nop,timestamp 754550 754808>
> > > > > 10:16:14.045104 IP 10.0.0.40.2616675590 > 10.0.0.30.2049: 112 acc=
ess fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
001F 001f
> > > > > 10:16:14.045402 IP 10.0.0.30.2049 > 10.0.0.40.2616675590: reply o=
k 124 access c 0003
> > > > > 10:16:14.047830 IP 10.0.0.40.2633452806 > 10.0.0.30.2049: 112 acc=
ess fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
001F 001f
> > > > > 10:16:14.048039 IP 10.0.0.30.2049 > 10.0.0.40.2633452806: reply o=
k 124 access c 0003
> > > > > 10:16:14.099385 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8553 wi=
n 2908 <nop,nop,timestamp 754592 754810>
> > > > > 10:16:14.293714 IP 10.0.0.40.2650230022 > 10.0.0.30.2049: 108 get=
attr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C74396000=
00000
> > > > > 10:16:14.294019 IP 10.0.0.30.2049 > 10.0.0.40.2650230022: reply o=
k 116 getattr DIR 40755 ids 0/0 sz 4096
> > > > > 10:16:14.297263 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8669 wi=
n 2908 <nop,nop,timestamp 754763 754871>
> > > > > 10:16:14.297272 IP 10.0.0.40.2667007238 > 10.0.0.30.2049: 112 acc=
ess fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
001F 001f
> > > > > 10:16:14.297466 IP 10.0.0.30.2049 > 10.0.0.40.2667007238: reply o=
k 124 access c 0003
> > > > > 10:16:14.297586 IP 10.0.0.40.2683784454 > 10.0.0.30.2049: 112 acc=
ess fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000=
001F 001f
> > > > > 10:16:14.297987 IP 10.0.0.30.2049 > 10.0.0.40.2683784454: reply o=
k 124 access c 0003
> > > > > 10:16:14.301165 IP 10.0.0.40.2700561670 > 10.0.0.30.2049: 104 acc=
ess fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000001F47219C8C0000=
0000 001f
> > > > > 10:16:14.301405 IP 10.0.0.30.2049 > 10.0.0.40.2700561670: reply o=
k 124 access c 0003
> > > > > 10:16:14.351229 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 9041 wi=
n 2908 <nop,nop,timestamp 754810 754873>
> > > > > 10:16:14.842633 IP 10.0.0.40.2717338886 > 10.0.0.30.2049: 100 get=
attr fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000047219C8C000=
00000
> > > > > 10:16:14.851711 IP 10.0.0.30.2049 > 10.0.0.40.2717338886: reply o=
k 116 getattr DIR 40755 ids 0/0 sz 4096
> > > > > 10:16:14.856846 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 9157 wi=
n 2908 <nop,nop,timestamp 755272 755008>
> > > > > =

> > > > > =

> > > > > > > does somebody have such setup up and running and can tell his=
 distro / kernel and nfs-utils version ?
> > > > > > > maybe i change distro then.
> > > > > > =

> > > > > > I doubt that it is a distro-specific thing.  As long as you have
> > > > > > nfs-utils-1.1.0 it should work.  I don't have a 10.3 box
> > > > > > set up yet, but it works fine on Debian/unstable for me.
> > > > > =

> > > > > ok, will try this on debian.
> > > > > =

> > > > > > Maybe try adding the "no_root_squash" export option.
> > > > > no difference
> > > > > =

> > > > > > What does "ls -l /export" on the server show?
> > > > > nothing unusual. no errors, just the dirs/mountpoints
> > > > > =

> > > > > Thanks for your help!
> > > > > =

> > > > > regards
> > > > > roland
> > > > > =

> > > > > =

> > > > > > =

> > > > > > On Saturday October 27, devzero@web.de wrote:
> > > > > > > Hello !
> > > > > > > =

> > > > > > > with 2.6.22 i`m trying to export loopback mounted iso-images.
> > > > > > > =

> > > > > > > this is /etc/exports:
> > > > > > > =

> > > > > > > /export *(ro,crossmnt,subtree_check)
> > > > > > =

> > > > > > I recommend replacing subtree_check with no_subtree_check, but =
it
> > > > > > shouldn't make an important difference in this case.
> > > > > > =

> > > > > > =

> > > > > > This should work with nfs-utils 1.1.0 or later.  With earlier r=
eleases
> > > > > > you need to explicitly export the subordinate filesystems too.
> > > > > > =

> > > > > > > =

> > > > > > > in /export, i have loopback mounted iso-images
> > > > > > > =

> > > > > > > after mounting on the client side under /mnt (tried one older=
 and one recent system) , i`m getting:
> > > > > > > =

> > > > > > > vmhost:/mnt # ls -la
> > > > > > > /bin/ls: iso1: Input/output error
> > > > > > > /bin/ls: iso2  Input/output error
> > > > > > > /bin/ls: iso3: Input/output error
> > > > > > > total 10128
> > > > > > > drwxrwxrwt   18 root root  270336 Oct 26 08:45 .
> > > > > > > drwxrwxrwt  186 root root   20760 Oct 27 17:45 ..
> > > > > > > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso1
> > > > > > > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso2
> > > > > > > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso3
> > > > > > > =

> > > > > > > vmhost:/mnt/iso1 # ls
> > > > > > > /bin/ls: .: Stale NFS file handle
> > > > > > > vmhost:/mnt/iso1 # ls -la
> > > > > > > /bin/ls: .: Input/output error
> > > > > > =

> > > > > > It is a little odd that the errors are inconsistent.
> > > > > > =

> > > > > > Can you find any log messages from mountd in syslog?  What do t=
hey
> > > > > > say?
> > > > > > Also what does
> > > > > >    cat /proc/fs/nfsd/exports
> > > > > > =

> > > > > > on the server show.
> > > > > > =

> > > > > > Finally, a tcpdump:
> > > > > > =

> > > > > >   tcpdump -s 0 -w /tmp/tcpdump port 2049
> > > > > > =

> > > > > > while you run the experiment might help.
> > > > > > =

> > > > > > > =

> > > > > > > i`m unsure if i should blame suse here (it`s an opensuse 10.3=
 box which seems to have nfs-utils 1.1.0)
> > > > > > > =

> > > > > > > does somebody have such setup up and running and can tell his=
 distro / kernel and nfs-utils version ?
> > > > > > > maybe i change distro then.
> > > > > > =

> > > > > > I doubt that it is a distro-specific thing.  As long as you have
> > > > > > nfs-utils-1.1.0 it should work.  I don't have a 10.3 box
> > > > > > set up yet, but it works fine on Debian/unstable for me.
> > > > > > =

> > > > > > Maybe try adding the "no_root_squash" export option.
> > > > > > What does "ls -l /export" on the server show?
> > > > > > =

> > > > > > NeilBrown
> > > > > > =

> > > > > =

> > > > > =

> > > > =

> > > > =

> > > > ___________________________________________________________________=
__
> > > > Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu spare=
n!
> > > > http://smartsurfer.web.de/?mc=3D100071&distributionid=3D000000000066
> > > > =

> > > > =

> > > > -------------------------------------------------------------------=
------
> > > > This SF.net email is sponsored by: Splunk Inc.
> > > > Still grepping through log files to find problems?  Stop.
> > > > Now Search log events and configuration files using AJAX and a brow=
ser.
> > > > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > > > _______________________________________________
> > > > NFS maillist  -  NFS@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/nfs
> > > =

> > =

> > =

> > _______________________________________________________________________=
___
> > Erweitern Sie FreeMail zu einem noch leistungsst=E4rkeren E-Mail-Postfa=
ch!		=

> > Mehr Infos unter http://produkte.web.de/club/?mc=3D021131
> > =

> =



_______________________________________________________________________
Jetzt neu! Sch=FCtzen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate
kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=3D022220


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 17+ messages in thread
* Re: stale nfs file handle with exported loopback mounts
@ 2007-11-10 15:14 devzero
  0 siblings, 0 replies; 17+ messages in thread
From: devzero @ 2007-11-10 15:14 UTC (permalink / raw)
  To: Neil Brown; +Cc: J. Bruce Fields, NFS

Hi Neil, =


as Andreas told that the kernel fix will be in one of the next openSuSE ker=
nel updates i`m wondering if that also applies to the mountd patch.
Will there be an update package for nfs-utils or is this just too minor iss=
ue for releasing an update package ?

regards
roland


> -----Urspr=FCngliche Nachricht-----
> Von: Neil Brown <neilb@suse.de>
> Gesendet: 01.11.07 05:26:50
> An: devzero@web.de
> CC: "J. Bruce Fields" <bfields@fieldses.org>, NFS@lists.sourceforge.net
> Betreff: Re: [NFS] stale nfs file handle with exported loopback mounts


> =

> On Wednesday October 31, devzero@web.de wrote:
> > ok, i just wanted to tell that this isn`t the right way to go imho.
> > =

> > some time ago i have tested exporting a parent dir containing
> > several loopback mounted iso images with some pre-1.1.0 nfs-utils
> > version and it worked - so =EC wonder why it now seems to have issues
> > as things should have gone stable..... =

> =

> We have a way of breaking things sometimes.... It's called
> "progress". :-)
> =

> The short answer is that there is a bug in mountd which is fixed by
> this patch:
> =

> diff --git a/utils/mountd/cache.c b/utils/mountd/cache.c
> index ce1a5a9..fd317cd 100644
> --- a/utils/mountd/cache.c
> +++ b/utils/mountd/cache.c
> @@ -508,7 +508,7 @@ void nfsd_fh(FILE *f)
>  	 */
>  	qword_printint(f, 0x7fffffff);
>  	if (found)
> -		qword_print(f, found->e_path);
> +		qword_print(f, found_path);
>  	qword_eol(f);
>   out:
>  	free(found_path);
> =

> =

> The longer answer is that there is also a bug in "mount.nfs" which is
> unrelated but was slowing me down in chasing this bug, and there is
> also a bug in the NFS client which was causing my client oops and need
> a reboot every time I triggered this bug in mountd, which further
> slowed me down.
> =

> The effect of this bug in mountd is that when the NFS client calls
> GETATTR on the root of the subordinate filesystem (e.g. your
> loop-mounted isos), it got attr information about the parent. ie. the
> top-level exported filesystem (/export in your case I think).
> This has a different 'fsid' than the nfs client was expecting and
> the NFS client got confused in various ways.
> =

> Thanks for your problem report - it helped find 3 bugs!
> =

> I'll get proper patches or bug report off to the relevant maintainers
> shortly.
> =

> NeilBrown
> =



_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=3D100071&distributionid=3D000000000066


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 17+ messages in thread
* Re: stale nfs file handle with exported loopback mounts
@ 2007-11-02 19:37 devzero
  2007-11-02 19:42 ` J. Bruce Fields
  0 siblings, 1 reply; 17+ messages in thread
From: devzero @ 2007-11-02 19:37 UTC (permalink / raw)
  To: J. Bruce Fields; +Cc: Neil Brown, NFS

so, you mean this is a problem of the client or some "fix it at the client =
end" ?

that would be bad, since it would mean i need to touch all our linux system=
s which want to access our next-generation :) cd-rom server.... =


anyway =


> > > after mounting for the first time on the client, i`m getting "Invalid=
 argument" for each loopback-mounted dir, if i do an ls -la on /mnt.
> > > this only happens _once_ and seems to be a server problem, because i =
can reboot the client and remount , i never see that errors again.

wondering, why doesn`t it happen again, even if i reboot the client.....

regards
roland



> -----Urspr=FCngliche Nachricht-----
> Von: "J. Bruce Fields" <bfields@fieldses.org>
> Gesendet: 02.11.07 20:24:52
> An: devzero@web.de
> CC: Neil Brown <neilb@suse.de>, NFS@lists.sourceforge.net
> Betreff: Re: [NFS] stale nfs file handle with exported loopback mounts


> =

> On Fri, Nov 02, 2007 at 03:23:17PM -0400, J. Bruce Fields wrote:
> > On Fri, Nov 02, 2007 at 08:06:58PM +0100, devzero@web.de wrote:
> > > hi!
> > > =

> > > it seems i was having weird mail problems with sending mails trough m=
y webmailer - at least two followups with attachments seem to be lost on se=
nding and are not in my sent folder anymore....
> > > =

> > > anyway - here is a second try, but probably worse than what i have wr=
itten before :)
> > > =

> > > =

> > > first off, thanks for the patch Neil, things look _much_ better now a=
nd exporting loopback mounts now basiscally works again.
> > > nice to see that my posting helped finding bugs.
> > > =

> > > maybe i have two more bugs for you :)
> > > =

> > > i have loopback mounts on the server and exported the parent dir with=
 crossmnt option.
> > > =

> > > after mounting for the first time on the client, i`m getting "Invalid=
 argument" for each loopback-mounted dir, if i do an ls -la on /mnt.
> > > this only happens _once_ and seems to be a server problem, because i =
can reboot the client and remount , i never see that errors again.
> > =

> > >From a quick look at the trace (thanks)--there's some getacl calls that
> > return EINVAL, then a few milliseconds later a second reply returns with
> > the original data.  That looks suspiciously like a reply being sent when
> > the request was also deferred pending the upcall to deal with the newly
> > encountered filesystem.  Sure enough, in
> > fs/nfs/nfs3acl.c:nfsd3_proc_getacl(), there's
> > =

> > 	 if ((nfserr =3D fh_verify(rqstp, &resp->fh, 0, MAY_NOP)))
> > 		RETURN_STATUS(nfserr_inval);
> > =

> > Change that nfserr_inval to an nfserr (here and in
> > fs/nfs/nfs2acl.c:nfsd_proc_getacl()), and maybe the problem will go
> > away.
> =

> (I've been seeing some odd spurious replayed replies in the nfsv4 case
> as well, by the way--I suspect it's a similar problem, but haven't had
> the chance to track it down yet....)
> =

> --b.
> =



_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=3D100071&distributionid=3D000000000066


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 17+ messages in thread
* Re: stale nfs file handle with exported loopback mounts
@ 2007-11-02 19:06 devzero
  2007-11-02 19:23 ` J. Bruce Fields
  0 siblings, 1 reply; 17+ messages in thread
From: devzero @ 2007-11-02 19:06 UTC (permalink / raw)
  To: Neil Brown; +Cc: J. Bruce Fields, NFS

hi!

it seems i was having weird mail problems with sending mails trough my webm=
ailer - at least two followups with attachments seem to be lost on sending =
and are not in my sent folder anymore....

anyway - here is a second try, but probably worse than what i have written =
before :)


first off, thanks for the patch Neil, things look _much_ better now and exp=
orting loopback mounts now basiscally works again.
nice to see that my posting helped finding bugs.

maybe i have two more bugs for you :)

i have loopback mounts on the server and exported the parent dir with cross=
mnt option.

after mounting for the first time on the client, i`m getting "Invalid argum=
ent" for each loopback-mounted dir, if i do an ls -la on /mnt.
this only happens _once_ and seems to be a server problem, because i can re=
boot the client and remount , i never see that errors again.

besides that, all seems to work fine.

as neil suggested, i have made a tcpdump of this available at:
http://82.141.46.148/bugs/nfs/tcpdump.out.bz2


furthermore, there is a very strange performance issue i was able to track =
down to uuid/blkid support.

i recognized this issue when i exported a directory containing a very large=
 number of loopback mounts via crossmnt export option.
ls -la on the clients mountpoint seemed to hung and i could see mountd bein=
g busy, eating 100% cpu for quite a while.

the time needed for ls to finish seems to grow exponentially with the numbe=
r of loopback-mounts inside the exported directory - i also tried with 1000=
 loopback mounts and mountd being busy for several minutes with this.

i have made a strace of mountd available at:
http://82.141.46.148/bugs/nfs/mountd.strace.txt.bz2

you can see that mountd seems to be busy doing the same things over and ove=
r again, looks that it does stat64() for all devices in /etc/blkid.tab for =
each loopback mount, weird.

here is some "strace -c -p $PID_OF_MOUNTD" for comparison -  without uuid/b=
lkid support compiled in it looks like this:

% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
 73.23    0.147722           2     66313           stat64
 10.37    0.020923          20      1031           write
  5.54    0.011179          23       494           select
  3.82    0.007699           5      1546           read
  3.04    0.006137           8       773           time
  2.18    0.004393           6       769           lstat64
  1.08    0.002182           4       519           munmap
  0.40    0.000797           1      1035           close
  0.29    0.000594           1      1034           open
  0.04    0.000089           0      1036           fstat64
  0.00    0.000000           0         2           alarm
  0.00    0.000000           0         3           _llseek
  0.00    0.000000           0         1           fdatasync
  0.00    0.000000           0         2           poll
  0.00    0.000000           0         2           rt_sigaction
  0.00    0.000000           0       521           mmap2
  0.00    0.000000           0         2           fcntl64
  0.00    0.000000           0         1           socket
  0.00    0.000000           0         1           connect
  0.00    0.000000           0         1           accept
  0.00    0.000000           0         2           send
------ ----------- ----------- --------- --------- ----------------
100.00    0.201715                 75088           total



this is an strace -c when uuid/blkid support is being compiled in:

% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
 61.64    1.008158           2    550916           stat64
 21.67    0.354441           9     37662           read
  5.65    0.092476          15      6377           getdents64
  4.06    0.066381           3     21395      8232 open
  1.62    0.026485           2     13169           fstat64
  1.36    0.022237           2     13164           close
  1.22    0.020025           2      8414           lstat64
  1.15    0.018805           4      4415           munmap
  0.27    0.004382          17       258           rename
  0.26    0.004329          17       258           unlink
  0.26    0.004305           2      2101           write
  0.23    0.003786           1      4380           fcntl64
  0.18    0.002899          11       262           select
  0.18    0.002883          11       258           access
  0.11    0.001857           0      4417           mmap2
  0.11    0.001765           0      4652           time
  0.01    0.000237           1       258           link
  0.00    0.000041           0       258           lseek
  0.00    0.000000           0         2           alarm
  0.00    0.000000           0         2           brk
  0.00    0.000000           0         1           gettimeofday
  0.00    0.000000           0       258           fchmod
  0.00    0.000000           0       265           _llseek
  0.00    0.000000           0         1           fdatasync
  0.00    0.000000           0         2           poll
  0.00    0.000000           0         1           prctl
  0.00    0.000000           0         2           rt_sigaction
  0.00    0.000000           0         1           getuid32
  0.00    0.000000           0         1           getgid32
  0.00    0.000000           0         1           geteuid32
  0.00    0.000000           0         1           getegid32
  0.00    0.000000           0         1           futex
  0.00    0.000000           0         1           socket
  0.00    0.000000           0         1           connect
  0.00    0.000000           0         1           accept
  0.00    0.000000           0         2           send
------ ----------- ----------- --------- --------- ----------------
100.00    1.635492                673158      8232 total

 =

as you can see there is an unusual high number of stat64() calls

server is opensuse 10.3 , client is suse 9.3 professional

if i can help resolving this issue, tell me what to do :)

regards
roland



> -----Urspr=FCngliche Nachricht-----
> Von: Neil Brown <neilb@suse.de>
> Gesendet: 01.11.07 05:26:50
> An: devzero@web.de
> CC: "J. Bruce Fields" <bfields@fieldses.org>, NFS@lists.sourceforge.net
> Betreff: Re: [NFS] stale nfs file handle with exported loopback mounts


> =

> On Wednesday October 31, devzero@web.de wrote:
> > ok, i just wanted to tell that this isn`t the right way to go imho.
> > =

> > some time ago i have tested exporting a parent dir containing
> > several loopback mounted iso images with some pre-1.1.0 nfs-utils
> > version and it worked - so =EC wonder why it now seems to have issues
> > as things should have gone stable..... =

> =

> We have a way of breaking things sometimes.... It's called
> "progress". :-)
> =

> The short answer is that there is a bug in mountd which is fixed by
> this patch:
> =

> diff --git a/utils/mountd/cache.c b/utils/mountd/cache.c
> index ce1a5a9..fd317cd 100644
> --- a/utils/mountd/cache.c
> +++ b/utils/mountd/cache.c
> @@ -508,7 +508,7 @@ void nfsd_fh(FILE *f)
>  	 */
>  	qword_printint(f, 0x7fffffff);
>  	if (found)
> -		qword_print(f, found->e_path);
> +		qword_print(f, found_path);
>  	qword_eol(f);
>   out:
>  	free(found_path);
> =

> =

> The longer answer is that there is also a bug in "mount.nfs" which is
> unrelated but was slowing me down in chasing this bug, and there is
> also a bug in the NFS client which was causing my client oops and need
> a reboot every time I triggered this bug in mountd, which further
> slowed me down.
> =

> The effect of this bug in mountd is that when the NFS client calls
> GETATTR on the root of the subordinate filesystem (e.g. your
> loop-mounted isos), it got attr information about the parent. ie. the
> top-level exported filesystem (/export in your case I think).
> This has a different 'fsid' than the nfs client was expecting and
> the NFS client got confused in various ways.
> =

> Thanks for your problem report - it helped find 3 bugs!
> =

> I'll get proper patches or bug report off to the relevant maintainers
> shortly.
> =

> NeilBrown
> =



_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=3D100071&distributionid=3D000000000066


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 17+ messages in thread
* Re: stale nfs file handle with exported loopback mounts
@ 2007-10-31 22:19 devzero
  2007-10-31 22:39 ` J. Bruce Fields
  0 siblings, 1 reply; 17+ messages in thread
From: devzero @ 2007-10-31 22:19 UTC (permalink / raw)
  To: J. Bruce Fields; +Cc: Neil Brown, NFS

>If you add an explicit export for each one, =

you mean, i should export each of those ~500 loopback mounted iso images ?
come on, that`s not what admins or users want, isn`t it ?

> -----Urspr=FCngliche Nachricht-----
> Von: "J. Bruce Fields" <bfields@fieldses.org>
> Gesendet: 31.10.07 21:58:00
> An: devzero@web.de
> CC: Neil Brown <neilb@suse.de>, NFS@lists.sourceforge.net
> Betreff: Re: [NFS] stale nfs file handle with exported loopback mounts


> =

> On Wed, Oct 31, 2007 at 09:46:13PM +0100, devzero@web.de wrote:
> > hi !
> > =

> > i tried latest grml build (lenny/sid) as server today (suse 9.3 as clie=
nt).
> > =

> > error still existing, but a little bit different:
> > =

> > if i cd to the loopback-mount dir`s on the client, i see the contents o=
f the parent directory, i.e. i get a recursion.
> =

> That suggests something funky in the way we're identifying those
> filesystems in the filehandle.  If you add an explicit export for each
> one, each with its own "fsid=3Dxyz" option (with xyz whatever positive
> integer you'd like, as long as it's difficult for export), does the
> problem go away??
> =

> --b.
> =

> > =

> > regards
> > roland
> > =

> > =

> > =

> > > -----Urspr=FCngliche Nachricht-----
> > > Von: devzero@web.de
> > > Gesendet: 30.10.07 21:05:56
> > > An: Neil Brown <neilb@suse.de>
> > > CC: NFS@lists.sourceforge.net
> > > Betreff: Re: [NFS] stale nfs file handle with exported loopback mounts
> > =

> > =

> > > =

> > > > I recommend replacing subtree_check with no_subtree_check, but it
> > > > shouldn't make an important difference in this case.
> > > =

> > > ok, i leave it as is.
> > > =

> > > > This should work with nfs-utils 1.1.0 or later.  With earlier relea=
ses
> > > > you need to explicitly export the subordinate filesystems too.
> > > > =

> > > =

> > > mhh - opensuse doesn`t have nfs-utils package, but it has nfs-client-=
1.1.0-8 which looks like they repackaged nfs-utils 1.1.0
> > > =

> > > > It is a little odd that the errors are inconsistent.
> > > =

> > > ok, but only a minor issue, if an issue at all, isn`t it ?
> > > =

> > > > Can you find any log messages from mountd in syslog?  What do they
> > > > say?
> > > =

> > > yes, on the client i`m getting :
> > > =

> > > Jun  3 21:36:01 linux kernel: nfs_update_inode: inode number mismatch
> > > Jun  3 21:36:01 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
> > > Jun  3 21:36:01 linux kernel: nfs_update_inode: inode number mismatch
> > > Jun  3 21:36:01 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
> > > Jun  3 21:36:17 linux kernel: nfs_update_inode: inode number mismatch
> > > Jun  3 21:36:17 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
> > > Jun  3 21:36:17 linux kernel: nfs_update_inode: inode number mismatch
> > > Jun  3 21:36:17 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
> > > Jun  3 21:36:20 linux kernel: nfs_update_inode: inode number mismatch
> > > Jun  3 21:36:20 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
> > > Jun  3 21:36:20 linux kernel: nfs_update_inode: inode number mismatch
> > > =

> > > =

> > > no error message on the server:
> > > Oct 26 10:09:31 opensuse103 mountd[4293]: authenticated unmount reque=
st from 10.0.0.40:1014 for /mnt (/mnt)
> > > Oct 26 10:10:07 opensuse103 mountd[4293]: authenticated mount request=
 from 10.0.0.40:612 for /mnt (/mnt)
> > > Oct 26 10:10:43 opensuse103 mountd[4293]: authenticated unmount reque=
st from 10.0.0.40:623 for /mnt (/mnt)
> > > Oct 26 10:10:52 opensuse103 mountd[4293]: authenticated mount request=
 from 10.0.0.40:624 for /mnt (/mnt)
> > > =

> > > > Also what does
> > > >    cat /proc/fs/nfsd/exports
> > > > =

> > > > on the server show.
> > > =

> > > opensuse103:~ # cat /proc/fs/nfsd/exports
> > > # Version 1.1
> > > # Path Client(Flags) # IPs
> > > /mnt/iso1       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D2c49f=
ef2:ba464293:9b2bf2b8:322ccbcb)
> > > /mnt/iso3       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D27ae9=
c67:0b794b36:8b5e9e17:37b569eb)
> > > /mnt    *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D08164ee4:2db1=
41eb:ac961701:49c74396)
> > > /mnt/iso2       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D2aad6=
ea5:a05d4441:b94c48e6:e5d9981e)
> > > =

> > > =

> > > > Finally, a tcpdump:
> > > > =

> > > >   tcpdump -s 0 -w /tmp/tcpdump port 2049
> > > > =

> > > > while you run the experiment might help.
> > > =

> > > ah - this seems to give a hint, but i don`t have a clue why the serve=
r (10.0.0.30) is telling the client (10.0.0.40) a "RPC Version mismatch".
> > > I also tried  --no-nfs-version 4 for rpc.mountd (setting in /etc/sysc=
onfig/nfs), but this didn`t make a difference.
> > > =

> > > here is the tcpdump output - i did =

> > > =

> > > - mount
> > > - ls / ls -la / cd to subdirs
> > > =

> > > 10:15:06.480542 IP 10.0.0.40.0 > 10.0.0.30.2049: 0 null
> > > 10:15:06.480572 IP 10.0.0.30.2049 > 10.0.0.40.0: reply ERR 0: RPC Ver=
sion mismatch (167772160-0)
> > > 10:15:06.480765 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 2031114913 =
win 1460 <nop,nop,timestamp 686128 737918>
> > > 10:15:06.480821 IP 10.0.0.40.2079804678 > 10.0.0.30.2049: 108 fsinfo =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743963CD81908
> > > 10:15:06.480833 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 108 win 181=
 <nop,nop,timestamp 737918 686128>
> > > 10:15:06.513365 IP 10.0.0.30.2049 > 10.0.0.40.2079804678: reply ok 84=
 fsinfo rtmax 65536 rtpref 65536 wtmax 65536 wtpref 65536 dtpref 4096
> > > 10:15:06.514408 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 85 win 1460=
 <nop,nop,timestamp 686160 737926>
> > > 10:15:06.514902 IP 10.0.0.40.2096581894 > 10.0.0.30.2049: 108 getattr=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743963CD81908
> > > 10:15:06.515256 IP 10.0.0.30.2049 > 10.0.0.40.2096581894: reply ok 11=
6 getattr DIR 40755 ids 0/0 sz 4096
> > > 10:15:06.553865 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 201 win 146=
0 <nop,nop,timestamp 686201 737926>
> > > 10:16:03.091784 IP 10.0.0.40.2113359110 > 10.0.0.30.2049: 108 getattr=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439647219C8C
> > > 10:16:03.093366 IP 10.0.0.30.2049 > 10.0.0.40.2113359110: reply ok 11=
6 getattr DIR 40755 ids 0/0 sz 4096
> > > 10:16:03.096046 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 317 win 146=
0 <nop,nop,timestamp 743610 752071>
> > > 10:16:03.097370 IP 10.0.0.40.2130136326 > 10.0.0.30.2049: 112 access =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F=
 001f
> > > 10:16:03.098156 IP 10.0.0.30.2049 > 10.0.0.40.2130136326: reply ok 12=
4 access c 0003
> > > 10:16:03.156812 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 441 win 146=
0 <nop,nop,timestamp 743651 752072>
> > > 10:16:08.967804 IP 10.0.0.40.2146913542 > 10.0.0.30.2049: 108 getattr=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
> > > 10:16:08.968305 IP 10.0.0.30.2049 > 10.0.0.40.2146913542: reply ok 11=
6 getattr DIR 40755 ids 0/0 sz 4096
> > > 10:16:08.974285 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 557 win 146=
0 <nop,nop,timestamp 749477 753540>
> > > 10:16:08.975739 IP 10.0.0.40.2163690758 > 10.0.0.30.2049: 132 readdir=
plus fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C74396000=
00000 512 bytes @ 0
> > > 10:16:08.975985 IP 10.0.0.30.2049 > 10.0.0.40.2163690758: reply ok 14=
48 readdirplus
> > > 10:16:08.976510 IP 10.0.0.30.2049 > 10.0.0.40.1684108288: reply Unkno=
wn rpc response code=3D2021855861 340
> > > 10:16:08.982238 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 2345 win 21=
84 <nop,nop,timestamp 749479 753541>
> > > 10:16:08.984415 IP 10.0.0.40.2180467974 > 10.0.0.30.2049: 116 lookup =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004=
 "iso3"
> > > 10:16:08.984931 IP 10.0.0.30.2049 > 10.0.0.40.2180467974: reply ok 23=
2 lookup fh Unknown/0100060027AE9C670B794B368B5E9E1737B569EB000000010000000=
2000041ED
> > > 10:16:09.008819 IP 10.0.0.40.2197245190 > 10.0.0.30.2049: 104 getattr=
 fh Unknown/0100060027AE9C670B794B368B5E9E1737B569EB0000000FDD22CC3C7002F0AC
> > > 10:16:09.010946 IP 10.0.0.30.2049 > 10.0.0.40.2197245190: reply ok 18=
8 getattr REG 2 ids 5/0 sz 0
> > > 10:16:09.032541 IP 10.0.0.40.2214022406 > 10.0.0.30.2049: 128 getattr=
 fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E66D0700
> > > 10:16:09.033405 IP 10.0.0.30.2049 > 10.0.0.40.2214022406: reply ok 18=
8 getattr REG 1 ids 1/0 sz 0
> > > 10:16:09.033490 IP 10.0.0.40.2230799622 > 10.0.0.30.2049: 128 getattr=
 fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E56D0700
> > > 10:16:09.036811 IP 10.0.0.30.2049 > 10.0.0.40.2230799622: reply ok 18=
8 getattr REG 1 ids 1/0 sz 0
> > > 10:16:09.037823 IP 10.0.0.40.2247576838 > 10.0.0.30.2049: 108 getattr=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
> > > 10:16:09.039817 IP 10.0.0.30.2049 > 10.0.0.40.2247576838: reply ok 11=
6 getattr DIR 40755 ids 0/0 sz 4096
> > > 10:16:09.040423 IP 10.0.0.40.2264354054 > 10.0.0.30.2049: 112 getattr=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000000F
> > > 10:16:09.040856 IP 10.0.0.30.2049 > 10.0.0.40.2264354054: reply ok 18=
8 getattr REG 2 ids 5/0 sz 0
> > > 10:16:09.041590 IP 10.0.0.40.2281131270 > 10.0.0.30.2049: 116 lookup =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004=
 "iso2"
> > > 10:16:09.041920 IP 10.0.0.30.2049 > 10.0.0.40.2281131270: reply ok 23=
2 lookup fh Unknown/010006002AAD6EA5A05D4441B94C48E6E5D9981E000000010000000=
2000041ED
> > > 10:16:09.049633 IP 10.0.0.40.2297908486 > 10.0.0.30.2049: 104 getattr=
 fh Unknown/010006002AAD6EA5A05D4441B94C48E6E5D9981E0000000F5FDC84454326E193
> > > 10:16:09.049781 IP 10.0.0.30.2049 > 10.0.0.40.2297908486: reply ok 18=
8 getattr REG 2 ids 5/0 sz 0
> > > 10:16:09.063218 IP 10.0.0.40.2314685702 > 10.0.0.30.2049: 128 getattr=
 fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E46D0700
> > > 10:16:09.072505 IP 10.0.0.30.2049 > 10.0.0.40.2314685702: reply ok 18=
8 getattr REG 1 ids 1/0 sz 0
> > > 10:16:09.091698 IP 10.0.0.40.2331462918 > 10.0.0.30.2049: 124 getattr=
 fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E46D0700
> > > 10:16:09.092022 IP 10.0.0.30.2049 > 10.0.0.40.2331462918: reply ok 11=
6 getattr REG 100644 ids 0/0 sz 1048576
> > > 10:16:09.128971 IP 10.0.0.40.2348240134 > 10.0.0.30.2049: 128 getattr=
 fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E36D0700
> > > 10:16:09.129304 IP 10.0.0.30.2049 > 10.0.0.40.2348240134: reply ok 18=
8 getattr REG 1 ids 1/0 sz 0
> > > 10:16:09.184155 IP 10.0.0.40.2365017350 > 10.0.0.30.2049: 124 getattr=
 fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E36D0700
> > > 10:16:09.184582 IP 10.0.0.30.2049 > 10.0.0.40.2365017350: reply ok 11=
6 getattr REG 100644 ids 0/0 sz 1048576
> > > 10:16:09.189234 IP 10.0.0.40.2381794566 > 10.0.0.30.2049: 116 lookup =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004=
 "iso1"
> > > 10:16:09.189435 IP 10.0.0.30.2049 > 10.0.0.40.2381794566: reply ok 23=
2 lookup fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB000000010000000=
2000041ED
> > > 10:16:09.193476 IP 10.0.0.40.2398571782 > 10.0.0.30.2049: 104 getattr=
 fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000F58896A884A0C62B7
> > > 10:16:09.193652 IP 10.0.0.30.2049 > 10.0.0.40.2398571782: reply ok 18=
8 getattr REG 2 ids 5/0 sz 0
> > > 10:16:09.194937 IP 10.0.0.40.2415348998 > 10.0.0.30.2049: 128 getattr=
 fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E76D0700
> > > 10:16:09.195033 IP 10.0.0.30.2049 > 10.0.0.40.2415348998: reply ok 18=
8 getattr REG 1 ids 1/0 sz 0
> > > 10:16:09.195230 IP 10.0.0.40.2432126214 > 10.0.0.30.2049: 128 getattr=
 fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E86D0700
> > > 10:16:09.323635 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 2572 win 41=
6 <nop,nop,timestamp 753629 749566>
> > > 10:16:09.324345 IP 10.0.0.30.2049 > 10.0.0.40.2432126214: reply ok 18=
8 getattr REG 1 ids 1/0 sz 0
> > > 10:16:09.341475 IP 10.0.0.40.2448903430 > 10.0.0.30.2049: 128 getattr=
 fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E26D0700
> > > 10:16:09.341524 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 2700 win 44=
9 <nop,nop,timestamp 753632 749707>
> > > 10:16:09.341928 IP 10.0.0.30.2049 > 10.0.0.40.2448903430: reply ok 18=
8 getattr REG 1 ids 1/0 sz 0
> > > 10:16:09.342117 IP 10.0.0.40.2465680646 > 10.0.0.30.2049: 124 getattr=
 fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E26D0700
> > > 10:16:09.343404 IP 10.0.0.30.2049 > 10.0.0.40.2465680646: reply ok 11=
6 getattr REG 100644 ids 0/0 sz 1048576
> > > 10:16:09.389316 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 5573 win 21=
84 <nop,nop,timestamp 749751 753633>
> > > 10:16:13.449513 IP 10.0.0.40.2482457862 > 10.0.0.30.2049: 108 getattr=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439647219CB5
> > > 10:16:13.449815 IP 10.0.0.30.2049 > 10.0.0.40.2482457862: reply ok 11=
6 getattr DIR 40755 ids 0/0 sz 4096
> > > 10:16:13.452344 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 5689 win 21=
84 <nop,nop,timestamp 753943 754660>
> > > 10:16:13.453973 IP 10.0.0.40.2499235078 > 10.0.0.30.2049: 100 getattr=
 fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB47219C8C0000000047219C8C
> > > 10:16:13.454154 IP 10.0.0.30.2049 > 10.0.0.40.2499235078: reply ok 11=
6 getattr DIR 40755 ids 0/0 sz 4096
> > > 10:16:13.456194 IP 10.0.0.40.2516012294 > 10.0.0.30.2049: 108 getattr=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439647219C8C
> > > 10:16:13.456361 IP 10.0.0.30.2049 > 10.0.0.40.2516012294: reply ok 11=
6 getattr DIR 40755 ids 0/0 sz 4096
> > > 10:16:13.458282 IP 10.0.0.40.2532789510 > 10.0.0.30.2049: 116 lookup =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004=
 "iso1"
> > > 10:16:13.458461 IP 10.0.0.30.2049 > 10.0.0.40.2532789510: reply ok 23=
2 lookup fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB000000010000000=
2000041ED
> > > 10:16:13.510637 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 6153 win 21=
84 <nop,nop,timestamp 753985 754662>
> > > 10:16:14.030110 IP 10.0.0.40.2549566726 > 10.0.0.30.2049: 112 access =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F=
 001f
> > > 10:16:14.030927 IP 10.0.0.30.2049 > 10.0.0.40.2549566726: reply ok 12=
4 access c 0003
> > > 10:16:14.033436 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 6277 win 21=
84 <nop,nop,timestamp 754548 754805>
> > > 10:16:14.034732 IP 10.0.0.40.2566343942 > 10.0.0.30.2049: 108 getattr=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
> > > 10:16:14.034980 IP 10.0.0.30.2049 > 10.0.0.40.2566343942: reply ok 11=
6 getattr DIR 40755 ids 0/0 sz 4096
> > > 10:16:14.037319 IP 10.0.0.40.2583121158 > 10.0.0.30.2049: 112 access =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F=
 001f
> > > 10:16:14.037486 IP 10.0.0.30.2049 > 10.0.0.40.2583121158: reply ok 12=
4 access c 0003
> > > 10:16:14.040323 IP 10.0.0.40.2599898374 > 10.0.0.30.2049: 132 readdir=
plus fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C74396000=
00000 512 bytes @ 0
> > > 10:16:14.040554 IP 10.0.0.30.2049 > 10.0.0.40.2599898374: reply ok 14=
48 readdirplus
> > > 10:16:14.041020 IP 10.0.0.30.2049 > 10.0.0.40.1684108288: reply Unkno=
wn rpc response code=3D2021855861 340
> > > 10:16:14.043583 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8305 win 29=
08 <nop,nop,timestamp 754550 754808>
> > > 10:16:14.045104 IP 10.0.0.40.2616675590 > 10.0.0.30.2049: 112 access =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F=
 001f
> > > 10:16:14.045402 IP 10.0.0.30.2049 > 10.0.0.40.2616675590: reply ok 12=
4 access c 0003
> > > 10:16:14.047830 IP 10.0.0.40.2633452806 > 10.0.0.30.2049: 112 access =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F=
 001f
> > > 10:16:14.048039 IP 10.0.0.30.2049 > 10.0.0.40.2633452806: reply ok 12=
4 access c 0003
> > > 10:16:14.099385 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8553 win 29=
08 <nop,nop,timestamp 754592 754810>
> > > 10:16:14.293714 IP 10.0.0.40.2650230022 > 10.0.0.30.2049: 108 getattr=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
> > > 10:16:14.294019 IP 10.0.0.30.2049 > 10.0.0.40.2650230022: reply ok 11=
6 getattr DIR 40755 ids 0/0 sz 4096
> > > 10:16:14.297263 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8669 win 29=
08 <nop,nop,timestamp 754763 754871>
> > > 10:16:14.297272 IP 10.0.0.40.2667007238 > 10.0.0.30.2049: 112 access =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F=
 001f
> > > 10:16:14.297466 IP 10.0.0.30.2049 > 10.0.0.40.2667007238: reply ok 12=
4 access c 0003
> > > 10:16:14.297586 IP 10.0.0.40.2683784454 > 10.0.0.30.2049: 112 access =
fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F=
 001f
> > > 10:16:14.297987 IP 10.0.0.30.2049 > 10.0.0.40.2683784454: reply ok 12=
4 access c 0003
> > > 10:16:14.301165 IP 10.0.0.40.2700561670 > 10.0.0.30.2049: 104 access =
fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000001F47219C8C00000000=
 001f
> > > 10:16:14.301405 IP 10.0.0.30.2049 > 10.0.0.40.2700561670: reply ok 12=
4 access c 0003
> > > 10:16:14.351229 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 9041 win 29=
08 <nop,nop,timestamp 754810 754873>
> > > 10:16:14.842633 IP 10.0.0.40.2717338886 > 10.0.0.30.2049: 100 getattr=
 fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000047219C8C00000000
> > > 10:16:14.851711 IP 10.0.0.30.2049 > 10.0.0.40.2717338886: reply ok 11=
6 getattr DIR 40755 ids 0/0 sz 4096
> > > 10:16:14.856846 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 9157 win 29=
08 <nop,nop,timestamp 755272 755008>
> > > =

> > > =

> > > > > does somebody have such setup up and running and can tell his dis=
tro / kernel and nfs-utils version ?
> > > > > maybe i change distro then.
> > > > =

> > > > I doubt that it is a distro-specific thing.  As long as you have
> > > > nfs-utils-1.1.0 it should work.  I don't have a 10.3 box
> > > > set up yet, but it works fine on Debian/unstable for me.
> > > =

> > > ok, will try this on debian.
> > > =

> > > > Maybe try adding the "no_root_squash" export option.
> > > no difference
> > > =

> > > > What does "ls -l /export" on the server show?
> > > nothing unusual. no errors, just the dirs/mountpoints
> > > =

> > > Thanks for your help!
> > > =

> > > regards
> > > roland
> > > =

> > > =

> > > > =

> > > > On Saturday October 27, devzero@web.de wrote:
> > > > > Hello !
> > > > > =

> > > > > with 2.6.22 i`m trying to export loopback mounted iso-images.
> > > > > =

> > > > > this is /etc/exports:
> > > > > =

> > > > > /export *(ro,crossmnt,subtree_check)
> > > > =

> > > > I recommend replacing subtree_check with no_subtree_check, but it
> > > > shouldn't make an important difference in this case.
> > > > =

> > > > =

> > > > This should work with nfs-utils 1.1.0 or later.  With earlier relea=
ses
> > > > you need to explicitly export the subordinate filesystems too.
> > > > =

> > > > > =

> > > > > in /export, i have loopback mounted iso-images
> > > > > =

> > > > > after mounting on the client side under /mnt (tried one older and=
 one recent system) , i`m getting:
> > > > > =

> > > > > vmhost:/mnt # ls -la
> > > > > /bin/ls: iso1: Input/output error
> > > > > /bin/ls: iso2  Input/output error
> > > > > /bin/ls: iso3: Input/output error
> > > > > total 10128
> > > > > drwxrwxrwt   18 root root  270336 Oct 26 08:45 .
> > > > > drwxrwxrwt  186 root root   20760 Oct 27 17:45 ..
> > > > > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso1
> > > > > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso2
> > > > > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso3
> > > > > =

> > > > > vmhost:/mnt/iso1 # ls
> > > > > /bin/ls: .: Stale NFS file handle
> > > > > vmhost:/mnt/iso1 # ls -la
> > > > > /bin/ls: .: Input/output error
> > > > =

> > > > It is a little odd that the errors are inconsistent.
> > > > =

> > > > Can you find any log messages from mountd in syslog?  What do they
> > > > say?
> > > > Also what does
> > > >    cat /proc/fs/nfsd/exports
> > > > =

> > > > on the server show.
> > > > =

> > > > Finally, a tcpdump:
> > > > =

> > > >   tcpdump -s 0 -w /tmp/tcpdump port 2049
> > > > =

> > > > while you run the experiment might help.
> > > > =

> > > > > =

> > > > > i`m unsure if i should blame suse here (it`s an opensuse 10.3 box=
 which seems to have nfs-utils 1.1.0)
> > > > > =

> > > > > does somebody have such setup up and running and can tell his dis=
tro / kernel and nfs-utils version ?
> > > > > maybe i change distro then.
> > > > =

> > > > I doubt that it is a distro-specific thing.  As long as you have
> > > > nfs-utils-1.1.0 it should work.  I don't have a 10.3 box
> > > > set up yet, but it works fine on Debian/unstable for me.
> > > > =

> > > > Maybe try adding the "no_root_squash" export option.
> > > > What does "ls -l /export" on the server show?
> > > > =

> > > > NeilBrown
> > > > =

> > > =

> > > =

> > =

> > =

> > _____________________________________________________________________
> > Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
> > http://smartsurfer.web.de/?mc=3D100071&distributionid=3D000000000066
> > =

> > =

> > -----------------------------------------------------------------------=
--
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > NFS maillist  -  NFS@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nfs
> =



__________________________________________________________________________
Erweitern Sie FreeMail zu einem noch leistungsst=E4rkeren E-Mail-Postfach!		=

Mehr Infos unter http://produkte.web.de/club/?mc=3D021131


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 17+ messages in thread
* Re: stale nfs file handle with exported loopback mounts
@ 2007-10-31 20:46 devzero
  2007-10-31 20:57 ` J. Bruce Fields
  0 siblings, 1 reply; 17+ messages in thread
From: devzero @ 2007-10-31 20:46 UTC (permalink / raw)
  To: Neil Brown; +Cc: NFS

hi !

i tried latest grml build (lenny/sid) as server today (suse 9.3 as client).

error still existing, but a little bit different:

if i cd to the loopback-mount dir`s on the client, i see the contents of th=
e parent directory, i.e. i get a recursion.

regards
roland



> -----Urspr=FCngliche Nachricht-----
> Von: devzero@web.de
> Gesendet: 30.10.07 21:05:56
> An: Neil Brown <neilb@suse.de>
> CC: NFS@lists.sourceforge.net
> Betreff: Re: [NFS] stale nfs file handle with exported loopback mounts


> =

> > I recommend replacing subtree_check with no_subtree_check, but it
> > shouldn't make an important difference in this case.
> =

> ok, i leave it as is.
> =

> > This should work with nfs-utils 1.1.0 or later.  With earlier releases
> > you need to explicitly export the subordinate filesystems too.
> > =

> =

> mhh - opensuse doesn`t have nfs-utils package, but it has nfs-client-1.1.=
0-8 which looks like they repackaged nfs-utils 1.1.0
> =

> > It is a little odd that the errors are inconsistent.
> =

> ok, but only a minor issue, if an issue at all, isn`t it ?
> =

> > Can you find any log messages from mountd in syslog?  What do they
> > say?
> =

> yes, on the client i`m getting :
> =

> Jun  3 21:36:01 linux kernel: nfs_update_inode: inode number mismatch
> Jun  3 21:36:01 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
> Jun  3 21:36:01 linux kernel: nfs_update_inode: inode number mismatch
> Jun  3 21:36:01 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
> Jun  3 21:36:17 linux kernel: nfs_update_inode: inode number mismatch
> Jun  3 21:36:17 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
> Jun  3 21:36:17 linux kernel: nfs_update_inode: inode number mismatch
> Jun  3 21:36:17 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
> Jun  3 21:36:20 linux kernel: nfs_update_inode: inode number mismatch
> Jun  3 21:36:20 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
> Jun  3 21:36:20 linux kernel: nfs_update_inode: inode number mismatch
> =

> =

> no error message on the server:
> Oct 26 10:09:31 opensuse103 mountd[4293]: authenticated unmount request f=
rom 10.0.0.40:1014 for /mnt (/mnt)
> Oct 26 10:10:07 opensuse103 mountd[4293]: authenticated mount request fro=
m 10.0.0.40:612 for /mnt (/mnt)
> Oct 26 10:10:43 opensuse103 mountd[4293]: authenticated unmount request f=
rom 10.0.0.40:623 for /mnt (/mnt)
> Oct 26 10:10:52 opensuse103 mountd[4293]: authenticated mount request fro=
m 10.0.0.40:624 for /mnt (/mnt)
> =

> > Also what does
> >    cat /proc/fs/nfsd/exports
> > =

> > on the server show.
> =

> opensuse103:~ # cat /proc/fs/nfsd/exports
> # Version 1.1
> # Path Client(Flags) # IPs
> /mnt/iso1       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D2c49fef2:=
ba464293:9b2bf2b8:322ccbcb)
> /mnt/iso3       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D27ae9c67:=
0b794b36:8b5e9e17:37b569eb)
> /mnt    *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D08164ee4:2db141eb=
:ac961701:49c74396)
> /mnt/iso2       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=3D2aad6ea5:=
a05d4441:b94c48e6:e5d9981e)
> =

> =

> > Finally, a tcpdump:
> > =

> >   tcpdump -s 0 -w /tmp/tcpdump port 2049
> > =

> > while you run the experiment might help.
> =

> ah - this seems to give a hint, but i don`t have a clue why the server (1=
0.0.0.30) is telling the client (10.0.0.40) a "RPC Version mismatch".
> I also tried  --no-nfs-version 4 for rpc.mountd (setting in /etc/sysconfi=
g/nfs), but this didn`t make a difference.
> =

> here is the tcpdump output - i did =

> =

> - mount
> - ls / ls -la / cd to subdirs
> =

> 10:15:06.480542 IP 10.0.0.40.0 > 10.0.0.30.2049: 0 null
> 10:15:06.480572 IP 10.0.0.30.2049 > 10.0.0.40.0: reply ERR 0: RPC Version=
 mismatch (167772160-0)
> 10:15:06.480765 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 2031114913 win =
1460 <nop,nop,timestamp 686128 737918>
> 10:15:06.480821 IP 10.0.0.40.2079804678 > 10.0.0.30.2049: 108 fsinfo fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C743963CD81908
> 10:15:06.480833 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 108 win 181 <no=
p,nop,timestamp 737918 686128>
> 10:15:06.513365 IP 10.0.0.30.2049 > 10.0.0.40.2079804678: reply ok 84 fsi=
nfo rtmax 65536 rtpref 65536 wtmax 65536 wtpref 65536 dtpref 4096
> 10:15:06.514408 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 85 win 1460 <no=
p,nop,timestamp 686160 737926>
> 10:15:06.514902 IP 10.0.0.40.2096581894 > 10.0.0.30.2049: 108 getattr fh =
Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743963CD81908
> 10:15:06.515256 IP 10.0.0.30.2049 > 10.0.0.40.2096581894: reply ok 116 ge=
tattr DIR 40755 ids 0/0 sz 4096
> 10:15:06.553865 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 201 win 1460 <n=
op,nop,timestamp 686201 737926>
> 10:16:03.091784 IP 10.0.0.40.2113359110 > 10.0.0.30.2049: 108 getattr fh =
Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439647219C8C
> 10:16:03.093366 IP 10.0.0.30.2049 > 10.0.0.40.2113359110: reply ok 116 ge=
tattr DIR 40755 ids 0/0 sz 4096
> 10:16:03.096046 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 317 win 1460 <n=
op,nop,timestamp 743610 752071>
> 10:16:03.097370 IP 10.0.0.40.2130136326 > 10.0.0.30.2049: 112 access fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
> 10:16:03.098156 IP 10.0.0.30.2049 > 10.0.0.40.2130136326: reply ok 124 ac=
cess c 0003
> 10:16:03.156812 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 441 win 1460 <n=
op,nop,timestamp 743651 752072>
> 10:16:08.967804 IP 10.0.0.40.2146913542 > 10.0.0.30.2049: 108 getattr fh =
Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
> 10:16:08.968305 IP 10.0.0.30.2049 > 10.0.0.40.2146913542: reply ok 116 ge=
tattr DIR 40755 ids 0/0 sz 4096
> 10:16:08.974285 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 557 win 1460 <n=
op,nop,timestamp 749477 753540>
> 10:16:08.975739 IP 10.0.0.40.2163690758 > 10.0.0.30.2049: 132 readdirplus=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000000=
0 512 bytes @ 0
> 10:16:08.975985 IP 10.0.0.30.2049 > 10.0.0.40.2163690758: reply ok 1448 r=
eaddirplus
> 10:16:08.976510 IP 10.0.0.30.2049 > 10.0.0.40.1684108288: reply Unknown r=
pc response code=3D2021855861 340
> 10:16:08.982238 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 2345 win 2184 <=
nop,nop,timestamp 749479 753541>
> 10:16:08.984415 IP 10.0.0.40.2180467974 > 10.0.0.30.2049: 116 lookup fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004 "is=
o3"
> 10:16:08.984931 IP 10.0.0.30.2049 > 10.0.0.40.2180467974: reply ok 232 lo=
okup fh Unknown/0100060027AE9C670B794B368B5E9E1737B569EB0000000100000002000=
041ED
> 10:16:09.008819 IP 10.0.0.40.2197245190 > 10.0.0.30.2049: 104 getattr fh =
Unknown/0100060027AE9C670B794B368B5E9E1737B569EB0000000FDD22CC3C7002F0AC
> 10:16:09.010946 IP 10.0.0.30.2049 > 10.0.0.40.2197245190: reply ok 188 ge=
tattr REG 2 ids 5/0 sz 0
> 10:16:09.032541 IP 10.0.0.40.2214022406 > 10.0.0.30.2049: 128 getattr fh =
Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E66D0700
> 10:16:09.033405 IP 10.0.0.30.2049 > 10.0.0.40.2214022406: reply ok 188 ge=
tattr REG 1 ids 1/0 sz 0
> 10:16:09.033490 IP 10.0.0.40.2230799622 > 10.0.0.30.2049: 128 getattr fh =
Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E56D0700
> 10:16:09.036811 IP 10.0.0.30.2049 > 10.0.0.40.2230799622: reply ok 188 ge=
tattr REG 1 ids 1/0 sz 0
> 10:16:09.037823 IP 10.0.0.40.2247576838 > 10.0.0.30.2049: 108 getattr fh =
Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
> 10:16:09.039817 IP 10.0.0.30.2049 > 10.0.0.40.2247576838: reply ok 116 ge=
tattr DIR 40755 ids 0/0 sz 4096
> 10:16:09.040423 IP 10.0.0.40.2264354054 > 10.0.0.30.2049: 112 getattr fh =
Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000000F
> 10:16:09.040856 IP 10.0.0.30.2049 > 10.0.0.40.2264354054: reply ok 188 ge=
tattr REG 2 ids 5/0 sz 0
> 10:16:09.041590 IP 10.0.0.40.2281131270 > 10.0.0.30.2049: 116 lookup fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004 "is=
o2"
> 10:16:09.041920 IP 10.0.0.30.2049 > 10.0.0.40.2281131270: reply ok 232 lo=
okup fh Unknown/010006002AAD6EA5A05D4441B94C48E6E5D9981E0000000100000002000=
041ED
> 10:16:09.049633 IP 10.0.0.40.2297908486 > 10.0.0.30.2049: 104 getattr fh =
Unknown/010006002AAD6EA5A05D4441B94C48E6E5D9981E0000000F5FDC84454326E193
> 10:16:09.049781 IP 10.0.0.30.2049 > 10.0.0.40.2297908486: reply ok 188 ge=
tattr REG 2 ids 5/0 sz 0
> 10:16:09.063218 IP 10.0.0.40.2314685702 > 10.0.0.30.2049: 128 getattr fh =
Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E46D0700
> 10:16:09.072505 IP 10.0.0.30.2049 > 10.0.0.40.2314685702: reply ok 188 ge=
tattr REG 1 ids 1/0 sz 0
> 10:16:09.091698 IP 10.0.0.40.2331462918 > 10.0.0.30.2049: 124 getattr fh =
Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E46D0700
> 10:16:09.092022 IP 10.0.0.30.2049 > 10.0.0.40.2331462918: reply ok 116 ge=
tattr REG 100644 ids 0/0 sz 1048576
> 10:16:09.128971 IP 10.0.0.40.2348240134 > 10.0.0.30.2049: 128 getattr fh =
Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E36D0700
> 10:16:09.129304 IP 10.0.0.30.2049 > 10.0.0.40.2348240134: reply ok 188 ge=
tattr REG 1 ids 1/0 sz 0
> 10:16:09.184155 IP 10.0.0.40.2365017350 > 10.0.0.30.2049: 124 getattr fh =
Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E36D0700
> 10:16:09.184582 IP 10.0.0.30.2049 > 10.0.0.40.2365017350: reply ok 116 ge=
tattr REG 100644 ids 0/0 sz 1048576
> 10:16:09.189234 IP 10.0.0.40.2381794566 > 10.0.0.30.2049: 116 lookup fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004 "is=
o1"
> 10:16:09.189435 IP 10.0.0.30.2049 > 10.0.0.40.2381794566: reply ok 232 lo=
okup fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000100000002000=
041ED
> 10:16:09.193476 IP 10.0.0.40.2398571782 > 10.0.0.30.2049: 104 getattr fh =
Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000F58896A884A0C62B7
> 10:16:09.193652 IP 10.0.0.30.2049 > 10.0.0.40.2398571782: reply ok 188 ge=
tattr REG 2 ids 5/0 sz 0
> 10:16:09.194937 IP 10.0.0.40.2415348998 > 10.0.0.30.2049: 128 getattr fh =
Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E76D0700
> 10:16:09.195033 IP 10.0.0.30.2049 > 10.0.0.40.2415348998: reply ok 188 ge=
tattr REG 1 ids 1/0 sz 0
> 10:16:09.195230 IP 10.0.0.40.2432126214 > 10.0.0.30.2049: 128 getattr fh =
Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E86D0700
> 10:16:09.323635 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 2572 win 416 <n=
op,nop,timestamp 753629 749566>
> 10:16:09.324345 IP 10.0.0.30.2049 > 10.0.0.40.2432126214: reply ok 188 ge=
tattr REG 1 ids 1/0 sz 0
> 10:16:09.341475 IP 10.0.0.40.2448903430 > 10.0.0.30.2049: 128 getattr fh =
Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E26D0700
> 10:16:09.341524 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 2700 win 449 <n=
op,nop,timestamp 753632 749707>
> 10:16:09.341928 IP 10.0.0.30.2049 > 10.0.0.40.2448903430: reply ok 188 ge=
tattr REG 1 ids 1/0 sz 0
> 10:16:09.342117 IP 10.0.0.40.2465680646 > 10.0.0.30.2049: 124 getattr fh =
Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E26D0700
> 10:16:09.343404 IP 10.0.0.30.2049 > 10.0.0.40.2465680646: reply ok 116 ge=
tattr REG 100644 ids 0/0 sz 1048576
> 10:16:09.389316 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 5573 win 2184 <=
nop,nop,timestamp 749751 753633>
> 10:16:13.449513 IP 10.0.0.40.2482457862 > 10.0.0.30.2049: 108 getattr fh =
Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439647219CB5
> 10:16:13.449815 IP 10.0.0.30.2049 > 10.0.0.40.2482457862: reply ok 116 ge=
tattr DIR 40755 ids 0/0 sz 4096
> 10:16:13.452344 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 5689 win 2184 <=
nop,nop,timestamp 753943 754660>
> 10:16:13.453973 IP 10.0.0.40.2499235078 > 10.0.0.30.2049: 100 getattr fh =
Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB47219C8C0000000047219C8C
> 10:16:13.454154 IP 10.0.0.30.2049 > 10.0.0.40.2499235078: reply ok 116 ge=
tattr DIR 40755 ids 0/0 sz 4096
> 10:16:13.456194 IP 10.0.0.40.2516012294 > 10.0.0.30.2049: 108 getattr fh =
Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439647219C8C
> 10:16:13.456361 IP 10.0.0.30.2049 > 10.0.0.40.2516012294: reply ok 116 ge=
tattr DIR 40755 ids 0/0 sz 4096
> 10:16:13.458282 IP 10.0.0.40.2532789510 > 10.0.0.30.2049: 116 lookup fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004 "is=
o1"
> 10:16:13.458461 IP 10.0.0.30.2049 > 10.0.0.40.2532789510: reply ok 232 lo=
okup fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000100000002000=
041ED
> 10:16:13.510637 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 6153 win 2184 <=
nop,nop,timestamp 753985 754662>
> 10:16:14.030110 IP 10.0.0.40.2549566726 > 10.0.0.30.2049: 112 access fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
> 10:16:14.030927 IP 10.0.0.30.2049 > 10.0.0.40.2549566726: reply ok 124 ac=
cess c 0003
> 10:16:14.033436 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 6277 win 2184 <=
nop,nop,timestamp 754548 754805>
> 10:16:14.034732 IP 10.0.0.40.2566343942 > 10.0.0.30.2049: 108 getattr fh =
Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
> 10:16:14.034980 IP 10.0.0.30.2049 > 10.0.0.40.2566343942: reply ok 116 ge=
tattr DIR 40755 ids 0/0 sz 4096
> 10:16:14.037319 IP 10.0.0.40.2583121158 > 10.0.0.30.2049: 112 access fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
> 10:16:14.037486 IP 10.0.0.30.2049 > 10.0.0.40.2583121158: reply ok 124 ac=
cess c 0003
> 10:16:14.040323 IP 10.0.0.40.2599898374 > 10.0.0.30.2049: 132 readdirplus=
 fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000000=
0 512 bytes @ 0
> 10:16:14.040554 IP 10.0.0.30.2049 > 10.0.0.40.2599898374: reply ok 1448 r=
eaddirplus
> 10:16:14.041020 IP 10.0.0.30.2049 > 10.0.0.40.1684108288: reply Unknown r=
pc response code=3D2021855861 340
> 10:16:14.043583 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8305 win 2908 <=
nop,nop,timestamp 754550 754808>
> 10:16:14.045104 IP 10.0.0.40.2616675590 > 10.0.0.30.2049: 112 access fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
> 10:16:14.045402 IP 10.0.0.30.2049 > 10.0.0.40.2616675590: reply ok 124 ac=
cess c 0003
> 10:16:14.047830 IP 10.0.0.40.2633452806 > 10.0.0.30.2049: 112 access fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
> 10:16:14.048039 IP 10.0.0.30.2049 > 10.0.0.40.2633452806: reply ok 124 ac=
cess c 0003
> 10:16:14.099385 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8553 win 2908 <=
nop,nop,timestamp 754592 754810>
> 10:16:14.293714 IP 10.0.0.40.2650230022 > 10.0.0.30.2049: 108 getattr fh =
Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
> 10:16:14.294019 IP 10.0.0.30.2049 > 10.0.0.40.2650230022: reply ok 116 ge=
tattr DIR 40755 ids 0/0 sz 4096
> 10:16:14.297263 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8669 win 2908 <=
nop,nop,timestamp 754763 754871>
> 10:16:14.297272 IP 10.0.0.40.2667007238 > 10.0.0.30.2049: 112 access fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
> 10:16:14.297466 IP 10.0.0.30.2049 > 10.0.0.40.2667007238: reply ok 124 ac=
cess c 0003
> 10:16:14.297586 IP 10.0.0.40.2683784454 > 10.0.0.30.2049: 112 access fh U=
nknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
> 10:16:14.297987 IP 10.0.0.30.2049 > 10.0.0.40.2683784454: reply ok 124 ac=
cess c 0003
> 10:16:14.301165 IP 10.0.0.40.2700561670 > 10.0.0.30.2049: 104 access fh U=
nknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000001F47219C8C00000000 001f
> 10:16:14.301405 IP 10.0.0.30.2049 > 10.0.0.40.2700561670: reply ok 124 ac=
cess c 0003
> 10:16:14.351229 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 9041 win 2908 <=
nop,nop,timestamp 754810 754873>
> 10:16:14.842633 IP 10.0.0.40.2717338886 > 10.0.0.30.2049: 100 getattr fh =
Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000047219C8C00000000
> 10:16:14.851711 IP 10.0.0.30.2049 > 10.0.0.40.2717338886: reply ok 116 ge=
tattr DIR 40755 ids 0/0 sz 4096
> 10:16:14.856846 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 9157 win 2908 <=
nop,nop,timestamp 755272 755008>
> =

> =

> > > does somebody have such setup up and running and can tell his distro =
/ kernel and nfs-utils version ?
> > > maybe i change distro then.
> > =

> > I doubt that it is a distro-specific thing.  As long as you have
> > nfs-utils-1.1.0 it should work.  I don't have a 10.3 box
> > set up yet, but it works fine on Debian/unstable for me.
> =

> ok, will try this on debian.
> =

> > Maybe try adding the "no_root_squash" export option.
> no difference
> =

> > What does "ls -l /export" on the server show?
> nothing unusual. no errors, just the dirs/mountpoints
> =

> Thanks for your help!
> =

> regards
> roland
> =

> =

> > =

> > On Saturday October 27, devzero@web.de wrote:
> > > Hello !
> > > =

> > > with 2.6.22 i`m trying to export loopback mounted iso-images.
> > > =

> > > this is /etc/exports:
> > > =

> > > /export *(ro,crossmnt,subtree_check)
> > =

> > I recommend replacing subtree_check with no_subtree_check, but it
> > shouldn't make an important difference in this case.
> > =

> > =

> > This should work with nfs-utils 1.1.0 or later.  With earlier releases
> > you need to explicitly export the subordinate filesystems too.
> > =

> > > =

> > > in /export, i have loopback mounted iso-images
> > > =

> > > after mounting on the client side under /mnt (tried one older and one=
 recent system) , i`m getting:
> > > =

> > > vmhost:/mnt # ls -la
> > > /bin/ls: iso1: Input/output error
> > > /bin/ls: iso2  Input/output error
> > > /bin/ls: iso3: Input/output error
> > > total 10128
> > > drwxrwxrwt   18 root root  270336 Oct 26 08:45 .
> > > drwxrwxrwt  186 root root   20760 Oct 27 17:45 ..
> > > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso1
> > > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso2
> > > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso3
> > > =

> > > vmhost:/mnt/iso1 # ls
> > > /bin/ls: .: Stale NFS file handle
> > > vmhost:/mnt/iso1 # ls -la
> > > /bin/ls: .: Input/output error
> > =

> > It is a little odd that the errors are inconsistent.
> > =

> > Can you find any log messages from mountd in syslog?  What do they
> > say?
> > Also what does
> >    cat /proc/fs/nfsd/exports
> > =

> > on the server show.
> > =

> > Finally, a tcpdump:
> > =

> >   tcpdump -s 0 -w /tmp/tcpdump port 2049
> > =

> > while you run the experiment might help.
> > =

> > > =

> > > i`m unsure if i should blame suse here (it`s an opensuse 10.3 box whi=
ch seems to have nfs-utils 1.1.0)
> > > =

> > > does somebody have such setup up and running and can tell his distro =
/ kernel and nfs-utils version ?
> > > maybe i change distro then.
> > =

> > I doubt that it is a distro-specific thing.  As long as you have
> > nfs-utils-1.1.0 it should work.  I don't have a 10.3 box
> > set up yet, but it works fine on Debian/unstable for me.
> > =

> > Maybe try adding the "no_root_squash" export option.
> > What does "ls -l /export" on the server show?
> > =

> > NeilBrown
> > =

> =

> =



_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=3D100071&distributionid=3D000000000066


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 17+ messages in thread
* Re: stale nfs file handle with exported loopback mounts
@ 2007-10-30 20:05 devzero
  0 siblings, 0 replies; 17+ messages in thread
From: devzero @ 2007-10-30 20:05 UTC (permalink / raw)
  To: Neil Brown; +Cc: NFS

> I recommend replacing subtree_check with no_subtree_check, but it
> shouldn't make an important difference in this case.

ok, i leave it as is.

> This should work with nfs-utils 1.1.0 or later.  With earlier releases
> you need to explicitly export the subordinate filesystems too.
> 

mhh - opensuse doesn`t have nfs-utils package, but it has nfs-client-1.1.0-8 which looks like they repackaged nfs-utils 1.1.0

> It is a little odd that the errors are inconsistent.

ok, but only a minor issue, if an issue at all, isn`t it ?

> Can you find any log messages from mountd in syslog?  What do they
> say?

yes, on the client i`m getting :

Jun  3 21:36:01 linux kernel: nfs_update_inode: inode number mismatch
Jun  3 21:36:01 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
Jun  3 21:36:01 linux kernel: nfs_update_inode: inode number mismatch
Jun  3 21:36:01 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
Jun  3 21:36:17 linux kernel: nfs_update_inode: inode number mismatch
Jun  3 21:36:17 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
Jun  3 21:36:17 linux kernel: nfs_update_inode: inode number mismatch
Jun  3 21:36:17 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
Jun  3 21:36:20 linux kernel: nfs_update_inode: inode number mismatch
Jun  3 21:36:20 linux kernel: expected (0:11/0x2), got (0:11/0x13881)
Jun  3 21:36:20 linux kernel: nfs_update_inode: inode number mismatch


no error message on the server:
Oct 26 10:09:31 opensuse103 mountd[4293]: authenticated unmount request from 10.0.0.40:1014 for /mnt (/mnt)
Oct 26 10:10:07 opensuse103 mountd[4293]: authenticated mount request from 10.0.0.40:612 for /mnt (/mnt)
Oct 26 10:10:43 opensuse103 mountd[4293]: authenticated unmount request from 10.0.0.40:623 for /mnt (/mnt)
Oct 26 10:10:52 opensuse103 mountd[4293]: authenticated mount request from 10.0.0.40:624 for /mnt (/mnt)

> Also what does
>    cat /proc/fs/nfsd/exports
> 
> on the server show.

opensuse103:~ # cat /proc/fs/nfsd/exports
# Version 1.1
# Path Client(Flags) # IPs
/mnt/iso1       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=2c49fef2:ba464293:9b2bf2b8:322ccbcb)
/mnt/iso3       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=27ae9c67:0b794b36:8b5e9e17:37b569eb)
/mnt    *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=08164ee4:2db141eb:ac961701:49c74396)
/mnt/iso2       *(ro,no_root_squash,sync,wdelay,crossmnt,uuid=2aad6ea5:a05d4441:b94c48e6:e5d9981e)


> Finally, a tcpdump:
> 
>   tcpdump -s 0 -w /tmp/tcpdump port 2049
> 
> while you run the experiment might help.

ah - this seems to give a hint, but i don`t have a clue why the server (10.0.0.30) is telling the client (10.0.0.40) a "RPC Version mismatch".
I also tried  --no-nfs-version 4 for rpc.mountd (setting in /etc/sysconfig/nfs), but this didn`t make a difference.

here is the tcpdump output - i did 

- mount
- ls / ls -la / cd to subdirs

10:15:06.480542 IP 10.0.0.40.0 > 10.0.0.30.2049: 0 null
10:15:06.480572 IP 10.0.0.30.2049 > 10.0.0.40.0: reply ERR 0: RPC Version mismatch (167772160-0)
10:15:06.480765 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 2031114913 win 1460 <nop,nop,timestamp 686128 737918>
10:15:06.480821 IP 10.0.0.40.2079804678 > 10.0.0.30.2049: 108 fsinfo fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743963CD81908
10:15:06.480833 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 108 win 181 <nop,nop,timestamp 737918 686128>
10:15:06.513365 IP 10.0.0.30.2049 > 10.0.0.40.2079804678: reply ok 84 fsinfo rtmax 65536 rtpref 65536 wtmax 65536 wtpref 65536 dtpref 4096
10:15:06.514408 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 85 win 1460 <nop,nop,timestamp 686160 737926>
10:15:06.514902 IP 10.0.0.40.2096581894 > 10.0.0.30.2049: 108 getattr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743963CD81908
10:15:06.515256 IP 10.0.0.30.2049 > 10.0.0.40.2096581894: reply ok 116 getattr DIR 40755 ids 0/0 sz 4096
10:15:06.553865 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 201 win 1460 <nop,nop,timestamp 686201 737926>
10:16:03.091784 IP 10.0.0.40.2113359110 > 10.0.0.30.2049: 108 getattr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439647219C8C
10:16:03.093366 IP 10.0.0.30.2049 > 10.0.0.40.2113359110: reply ok 116 getattr DIR 40755 ids 0/0 sz 4096
10:16:03.096046 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 317 win 1460 <nop,nop,timestamp 743610 752071>
10:16:03.097370 IP 10.0.0.40.2130136326 > 10.0.0.30.2049: 112 access fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
10:16:03.098156 IP 10.0.0.30.2049 > 10.0.0.40.2130136326: reply ok 124 access c 0003
10:16:03.156812 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 441 win 1460 <nop,nop,timestamp 743651 752072>
10:16:08.967804 IP 10.0.0.40.2146913542 > 10.0.0.30.2049: 108 getattr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
10:16:08.968305 IP 10.0.0.30.2049 > 10.0.0.40.2146913542: reply ok 116 getattr DIR 40755 ids 0/0 sz 4096
10:16:08.974285 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 557 win 1460 <nop,nop,timestamp 749477 753540>
10:16:08.975739 IP 10.0.0.40.2163690758 > 10.0.0.30.2049: 132 readdirplus fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000 512 bytes @ 0
10:16:08.975985 IP 10.0.0.30.2049 > 10.0.0.40.2163690758: reply ok 1448 readdirplus
10:16:08.976510 IP 10.0.0.30.2049 > 10.0.0.40.1684108288: reply Unknown rpc response code=2021855861 340
10:16:08.982238 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 2345 win 2184 <nop,nop,timestamp 749479 753541>
10:16:08.984415 IP 10.0.0.40.2180467974 > 10.0.0.30.2049: 116 lookup fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004 "iso3"
10:16:08.984931 IP 10.0.0.30.2049 > 10.0.0.40.2180467974: reply ok 232 lookup fh Unknown/0100060027AE9C670B794B368B5E9E1737B569EB0000000100000002000041ED
10:16:09.008819 IP 10.0.0.40.2197245190 > 10.0.0.30.2049: 104 getattr fh Unknown/0100060027AE9C670B794B368B5E9E1737B569EB0000000FDD22CC3C7002F0AC
10:16:09.010946 IP 10.0.0.30.2049 > 10.0.0.40.2197245190: reply ok 188 getattr REG 2 ids 5/0 sz 0
10:16:09.032541 IP 10.0.0.40.2214022406 > 10.0.0.30.2049: 128 getattr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E66D0700
10:16:09.033405 IP 10.0.0.30.2049 > 10.0.0.40.2214022406: reply ok 188 getattr REG 1 ids 1/0 sz 0
10:16:09.033490 IP 10.0.0.40.2230799622 > 10.0.0.30.2049: 128 getattr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E56D0700
10:16:09.036811 IP 10.0.0.30.2049 > 10.0.0.40.2230799622: reply ok 188 getattr REG 1 ids 1/0 sz 0
10:16:09.037823 IP 10.0.0.40.2247576838 > 10.0.0.30.2049: 108 getattr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
10:16:09.039817 IP 10.0.0.30.2049 > 10.0.0.40.2247576838: reply ok 116 getattr DIR 40755 ids 0/0 sz 4096
10:16:09.040423 IP 10.0.0.40.2264354054 > 10.0.0.30.2049: 112 getattr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000000F
10:16:09.040856 IP 10.0.0.30.2049 > 10.0.0.40.2264354054: reply ok 188 getattr REG 2 ids 5/0 sz 0
10:16:09.041590 IP 10.0.0.40.2281131270 > 10.0.0.30.2049: 116 lookup fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004 "iso2"
10:16:09.041920 IP 10.0.0.30.2049 > 10.0.0.40.2281131270: reply ok 232 lookup fh Unknown/010006002AAD6EA5A05D4441B94C48E6E5D9981E0000000100000002000041ED
10:16:09.049633 IP 10.0.0.40.2297908486 > 10.0.0.30.2049: 104 getattr fh Unknown/010006002AAD6EA5A05D4441B94C48E6E5D9981E0000000F5FDC84454326E193
10:16:09.049781 IP 10.0.0.30.2049 > 10.0.0.40.2297908486: reply ok 188 getattr REG 2 ids 5/0 sz 0
10:16:09.063218 IP 10.0.0.40.2314685702 > 10.0.0.30.2049: 128 getattr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E46D0700
10:16:09.072505 IP 10.0.0.30.2049 > 10.0.0.40.2314685702: reply ok 188 getattr REG 1 ids 1/0 sz 0
10:16:09.091698 IP 10.0.0.40.2331462918 > 10.0.0.30.2049: 124 getattr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E46D0700
10:16:09.092022 IP 10.0.0.30.2049 > 10.0.0.40.2331462918: reply ok 116 getattr REG 100644 ids 0/0 sz 1048576
10:16:09.128971 IP 10.0.0.40.2348240134 > 10.0.0.30.2049: 128 getattr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E36D0700
10:16:09.129304 IP 10.0.0.30.2049 > 10.0.0.40.2348240134: reply ok 188 getattr REG 1 ids 1/0 sz 0
10:16:09.184155 IP 10.0.0.40.2365017350 > 10.0.0.30.2049: 124 getattr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E36D0700
10:16:09.184582 IP 10.0.0.30.2049 > 10.0.0.40.2365017350: reply ok 116 getattr REG 100644 ids 0/0 sz 1048576
10:16:09.189234 IP 10.0.0.40.2381794566 > 10.0.0.30.2049: 116 lookup fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004 "iso1"
10:16:09.189435 IP 10.0.0.30.2049 > 10.0.0.40.2381794566: reply ok 232 lookup fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000100000002000041ED
10:16:09.193476 IP 10.0.0.40.2398571782 > 10.0.0.30.2049: 104 getattr fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000F58896A884A0C62B7
10:16:09.193652 IP 10.0.0.30.2049 > 10.0.0.40.2398571782: reply ok 188 getattr REG 2 ids 5/0 sz 0
10:16:09.194937 IP 10.0.0.40.2415348998 > 10.0.0.30.2049: 128 getattr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E76D0700
10:16:09.195033 IP 10.0.0.30.2049 > 10.0.0.40.2415348998: reply ok 188 getattr REG 1 ids 1/0 sz 0
10:16:09.195230 IP 10.0.0.40.2432126214 > 10.0.0.30.2049: 128 getattr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E86D0700
10:16:09.323635 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 2572 win 416 <nop,nop,timestamp 753629 749566>
10:16:09.324345 IP 10.0.0.30.2049 > 10.0.0.40.2432126214: reply ok 188 getattr REG 1 ids 1/0 sz 0
10:16:09.341475 IP 10.0.0.40.2448903430 > 10.0.0.30.2049: 128 getattr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E26D0700
10:16:09.341524 IP 10.0.0.30.2049 > 10.0.0.40.1022: . ack 2700 win 449 <nop,nop,timestamp 753632 749707>
10:16:09.341928 IP 10.0.0.30.2049 > 10.0.0.40.2448903430: reply ok 188 getattr REG 1 ids 1/0 sz 0
10:16:09.342117 IP 10.0.0.40.2465680646 > 10.0.0.30.2049: 124 getattr fh Unknown/01000702813801000000000008164EE42DB141EBAC96170149C74396E26D0700
10:16:09.343404 IP 10.0.0.30.2049 > 10.0.0.40.2465680646: reply ok 116 getattr REG 100644 ids 0/0 sz 1048576
10:16:09.389316 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 5573 win 2184 <nop,nop,timestamp 749751 753633>
10:16:13.449513 IP 10.0.0.40.2482457862 > 10.0.0.30.2049: 108 getattr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439647219CB5
10:16:13.449815 IP 10.0.0.30.2049 > 10.0.0.40.2482457862: reply ok 116 getattr DIR 40755 ids 0/0 sz 4096
10:16:13.452344 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 5689 win 2184 <nop,nop,timestamp 753943 754660>
10:16:13.453973 IP 10.0.0.40.2499235078 > 10.0.0.30.2049: 100 getattr fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB47219C8C0000000047219C8C
10:16:13.454154 IP 10.0.0.30.2049 > 10.0.0.40.2499235078: reply ok 116 getattr DIR 40755 ids 0/0 sz 4096
10:16:13.456194 IP 10.0.0.40.2516012294 > 10.0.0.30.2049: 108 getattr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439647219C8C
10:16:13.456361 IP 10.0.0.30.2049 > 10.0.0.40.2516012294: reply ok 116 getattr DIR 40755 ids 0/0 sz 4096
10:16:13.458282 IP 10.0.0.40.2532789510 > 10.0.0.30.2049: 116 lookup fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000004 "iso1"
10:16:13.458461 IP 10.0.0.30.2049 > 10.0.0.40.2532789510: reply ok 232 lookup fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000100000002000041ED
10:16:13.510637 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 6153 win 2184 <nop,nop,timestamp 753985 754662>
10:16:14.030110 IP 10.0.0.40.2549566726 > 10.0.0.30.2049: 112 access fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
10:16:14.030927 IP 10.0.0.30.2049 > 10.0.0.40.2549566726: reply ok 124 access c 0003
10:16:14.033436 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 6277 win 2184 <nop,nop,timestamp 754548 754805>
10:16:14.034732 IP 10.0.0.40.2566343942 > 10.0.0.30.2049: 108 getattr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
10:16:14.034980 IP 10.0.0.30.2049 > 10.0.0.40.2566343942: reply ok 116 getattr DIR 40755 ids 0/0 sz 4096
10:16:14.037319 IP 10.0.0.40.2583121158 > 10.0.0.30.2049: 112 access fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
10:16:14.037486 IP 10.0.0.30.2049 > 10.0.0.40.2583121158: reply ok 124 access c 0003
10:16:14.040323 IP 10.0.0.40.2599898374 > 10.0.0.30.2049: 132 readdirplus fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000 512 bytes @ 0
10:16:14.040554 IP 10.0.0.30.2049 > 10.0.0.40.2599898374: reply ok 1448 readdirplus
10:16:14.041020 IP 10.0.0.30.2049 > 10.0.0.40.1684108288: reply Unknown rpc response code=2021855861 340
10:16:14.043583 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8305 win 2908 <nop,nop,timestamp 754550 754808>
10:16:14.045104 IP 10.0.0.40.2616675590 > 10.0.0.30.2049: 112 access fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
10:16:14.045402 IP 10.0.0.30.2049 > 10.0.0.40.2616675590: reply ok 124 access c 0003
10:16:14.047830 IP 10.0.0.40.2633452806 > 10.0.0.30.2049: 112 access fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
10:16:14.048039 IP 10.0.0.30.2049 > 10.0.0.40.2633452806: reply ok 124 access c 0003
10:16:14.099385 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8553 win 2908 <nop,nop,timestamp 754592 754810>
10:16:14.293714 IP 10.0.0.40.2650230022 > 10.0.0.30.2049: 108 getattr fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C7439600000000
10:16:14.294019 IP 10.0.0.30.2049 > 10.0.0.40.2650230022: reply ok 116 getattr DIR 40755 ids 0/0 sz 4096
10:16:14.297263 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 8669 win 2908 <nop,nop,timestamp 754763 754871>
10:16:14.297272 IP 10.0.0.40.2667007238 > 10.0.0.30.2049: 112 access fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
10:16:14.297466 IP 10.0.0.30.2049 > 10.0.0.40.2667007238: reply ok 124 access c 0003
10:16:14.297586 IP 10.0.0.40.2683784454 > 10.0.0.30.2049: 112 access fh Unknown/01000700813801000000000008164EE42DB141EBAC96170149C743960000001F 001f
10:16:14.297987 IP 10.0.0.30.2049 > 10.0.0.40.2683784454: reply ok 124 access c 0003
10:16:14.301165 IP 10.0.0.40.2700561670 > 10.0.0.30.2049: 104 access fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000001F47219C8C00000000 001f
10:16:14.301405 IP 10.0.0.30.2049 > 10.0.0.40.2700561670: reply ok 124 access c 0003
10:16:14.351229 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 9041 win 2908 <nop,nop,timestamp 754810 754873>
10:16:14.842633 IP 10.0.0.40.2717338886 > 10.0.0.30.2049: 100 getattr fh Unknown/010006002C49FEF2BA4642939B2BF2B8322CCBCB0000000047219C8C00000000
10:16:14.851711 IP 10.0.0.30.2049 > 10.0.0.40.2717338886: reply ok 116 getattr DIR 40755 ids 0/0 sz 4096
10:16:14.856846 IP 10.0.0.40.1022 > 10.0.0.30.2049: . ack 9157 win 2908 <nop,nop,timestamp 755272 755008>


> > does somebody have such setup up and running and can tell his distro / kernel and nfs-utils version ?
> > maybe i change distro then.
> 
> I doubt that it is a distro-specific thing.  As long as you have
> nfs-utils-1.1.0 it should work.  I don't have a 10.3 box
> set up yet, but it works fine on Debian/unstable for me.

ok, will try this on debian.

> Maybe try adding the "no_root_squash" export option.
no difference

> What does "ls -l /export" on the server show?
nothing unusual. no errors, just the dirs/mountpoints

Thanks for your help!

regards
roland


> 
> On Saturday October 27, devzero@web.de wrote:
> > Hello !
> > 
> > with 2.6.22 i`m trying to export loopback mounted iso-images.
> > 
> > this is /etc/exports:
> > 
> > /export *(ro,crossmnt,subtree_check)
> 
> I recommend replacing subtree_check with no_subtree_check, but it
> shouldn't make an important difference in this case.
> 
> 
> This should work with nfs-utils 1.1.0 or later.  With earlier releases
> you need to explicitly export the subordinate filesystems too.
> 
> > 
> > in /export, i have loopback mounted iso-images
> > 
> > after mounting on the client side under /mnt (tried one older and one recent system) , i`m getting:
> > 
> > vmhost:/mnt # ls -la
> > /bin/ls: iso1: Input/output error
> > /bin/ls: iso2  Input/output error
> > /bin/ls: iso3: Input/output error
> > total 10128
> > drwxrwxrwt   18 root root  270336 Oct 26 08:45 .
> > drwxrwxrwt  186 root root   20760 Oct 27 17:45 ..
> > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso1
> > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso2
> > drwxr-xr-x    2 root root   16384 Jan  1  1970 iso3
> > 
> > vmhost:/mnt/iso1 # ls
> > /bin/ls: .: Stale NFS file handle
> > vmhost:/mnt/iso1 # ls -la
> > /bin/ls: .: Input/output error
> 
> It is a little odd that the errors are inconsistent.
> 
> Can you find any log messages from mountd in syslog?  What do they
> say?
> Also what does
>    cat /proc/fs/nfsd/exports
> 
> on the server show.
> 
> Finally, a tcpdump:
> 
>   tcpdump -s 0 -w /tmp/tcpdump port 2049
> 
> while you run the experiment might help.
> 
> > 
> > i`m unsure if i should blame suse here (it`s an opensuse 10.3 box which seems to have nfs-utils 1.1.0)
> > 
> > does somebody have such setup up and running and can tell his distro / kernel and nfs-utils version ?
> > maybe i change distro then.
> 
> I doubt that it is a distro-specific thing.  As long as you have
> nfs-utils-1.1.0 it should work.  I don't have a 10.3 box
> set up yet, but it works fine on Debian/unstable for me.
> 
> Maybe try adding the "no_root_squash" export option.
> What does "ls -l /export" on the server show?
> 
> NeilBrown
> 


_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! 
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 17+ messages in thread
* stale nfs file handle with exported loopback mounts
@ 2007-10-27 16:13 devzero
  2007-10-30  5:14 ` Neil Brown
  0 siblings, 1 reply; 17+ messages in thread
From: devzero @ 2007-10-27 16:13 UTC (permalink / raw)
  To: NFS

Hello !

with 2.6.22 i`m trying to export loopback mounted iso-images.

this is /etc/exports:

/export *(ro,crossmnt,subtree_check)

in /export, i have loopback mounted iso-images

after mounting on the client side under /mnt (tried one older and one recent system) , i`m getting:

vmhost:/mnt # ls -la
/bin/ls: iso1: Input/output error
/bin/ls: iso2  Input/output error
/bin/ls: iso3: Input/output error
total 10128
drwxrwxrwt   18 root root  270336 Oct 26 08:45 .
drwxrwxrwt  186 root root   20760 Oct 27 17:45 ..
drwxr-xr-x    2 root root   16384 Jan  1  1970 iso1
drwxr-xr-x    2 root root   16384 Jan  1  1970 iso2
drwxr-xr-x    2 root root   16384 Jan  1  1970 iso3

vmhost:/mnt/iso1 # ls
/bin/ls: .: Stale NFS file handle
vmhost:/mnt/iso1 # ls -la
/bin/ls: .: Input/output error

i`m unsure if i should blame suse here (it`s an opensuse 10.3 box which seems to have nfs-utils 1.1.0)

does somebody have such setup up and running and can tell his distro / kernel and nfs-utils version ?
maybe i change distro then.

any clues what`s going wrong here and how to resolve ?

regards
roland

_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

^ permalink raw reply	[flat|nested] 17+ messages in thread

end of thread, other threads:[~2007-11-10 15:14 UTC | newest]

Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-31 22:50 stale nfs file handle with exported loopback mounts devzero
2007-11-01  4:26 ` Neil Brown
  -- strict thread matches above, loose matches on Subject: below --
2007-11-10 15:14 devzero
2007-11-02 19:37 devzero
2007-11-02 19:42 ` J. Bruce Fields
2007-11-04 20:30   ` J. Bruce Fields
2007-11-05  9:59     ` Andreas Gruenbacher
2007-11-02 19:06 devzero
2007-11-02 19:23 ` J. Bruce Fields
2007-11-02 19:24   ` J. Bruce Fields
2007-10-31 22:19 devzero
2007-10-31 22:39 ` J. Bruce Fields
2007-10-31 20:46 devzero
2007-10-31 20:57 ` J. Bruce Fields
2007-10-30 20:05 devzero
2007-10-27 16:13 devzero
2007-10-30  5:14 ` Neil Brown

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.