Linux NFS development
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: linux-nfs@vger.kernel.org
Subject: 2.6.24-rc3 unable to mount something which should use nohide
Date: Thu, 29 Nov 2007 11:44:59 -0500	[thread overview]
Message-ID: <1196354699.2912.57.camel@localhost.localdomain> (raw)

NFS server "paris" (some 2.6.18 based kernel):

[root@paris ~]# mount | grep storage
/dev/mapper/StorageVG01-LogVol00 on /export/storage type ext3 (rw)
/dev/mapper/KernelVG01-LogVol00 on /export/storage/kernel type ext3 (rw)
[root@paris ~]# cat /etc/exports
/export/storage         *(rw,sync,all_squash,anonuid=500,anongid=500)
/export/storage/kernel  *(rw,sync,all_squash,anonuid=500,anongid=500,nohide)

On my clients x86_64 running an almost clean-from-git 2.6.24-rc3 kernel:

[root@dhcp231-145 ~]# mount -o noatime paris:/export/storage /storage
[root@dhcp231-145 ~]# ls /storage/kernel
ls: cannot access /storage/kernel: Stale NFS file handle

(notice /storage/kernel should be triggering that nohide mount
for /export/storage/kernel) so I figured maybe that automatic nohide
stuff was broken.  I'll try by hand:

[root@dhcp231-145 ~]# mount paris:/export/storage/kernel /storage/kernel
mount.nfs: Stale NFS file handle

Same thing.  Nothing in dmesg or /var/log/messages.  I know this worked
not long ago....

-Eric


             reply	other threads:[~2007-11-29 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 16:44 Eric Paris [this message]
     [not found] ` <1196354699.2912.57.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-11-29 17:41   ` 2.6.24-rc3 unable to mount something which should use nohide Trond Myklebust
     [not found]     ` <1196358095.7808.24.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2007-11-29 18:03       ` Eric Paris

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=1196354699.2912.57.camel@localhost.localdomain \
    --to=eparis@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox