From: Neil Brown <neilb@suse.de>
To: devzero@web.de
Cc: NFS@lists.sourceforge.net
Subject: Re: stale nfs file handle with exported loopback mounts
Date: Tue, 30 Oct 2007 16:14:51 +1100 [thread overview]
Message-ID: <18214.48587.2205.753253@notabene.brown> (raw)
In-Reply-To: message from devzero@web.de on Saturday October 27
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
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-10-30 5:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 16:13 stale nfs file handle with exported loopback mounts devzero
2007-10-30 5:14 ` Neil Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-30 20:05 devzero
2007-10-31 20:46 devzero
2007-10-31 20:57 ` J. Bruce Fields
2007-10-31 22:19 devzero
2007-10-31 22:39 ` J. Bruce Fields
2007-10-31 22:50 devzero
2007-11-01 4:26 ` Neil Brown
2007-11-02 19:06 devzero
2007-11-02 19:23 ` J. Bruce Fields
2007-11-02 19:24 ` J. Bruce Fields
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-10 15:14 devzero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18214.48587.2205.753253@notabene.brown \
--to=neilb@suse.de \
--cc=NFS@lists.sourceforge.net \
--cc=devzero@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.