From: Michael Haverkamp <mhaverkamp@kcp.com>
To: Hugh Caley <Hugh_Caley@affymetrix.com>, nfs@lists.sourceforge.net
Subject: Re: Stale NFS Filehandles and Permission Denied on 2.6.9
Date: Tue, 23 Nov 2004 08:06:00 -0600 [thread overview]
Message-ID: <41A343C8.7090106@kcp.com> (raw)
In-Reply-To: <41A28FE0.9070906@affymetrix.com>
I had similar problems. Downgrading to kernel 2.6.7 and using
no_subtree_check seemed to fix it for me. I'm not sure which one fixed
it, or if it was both.
Hugh Caley wrote:
> We recently migrated our main storage to a Nexsan Atabeast fronted by
> two PC's running Fedora Core 2. We are being plagued by "Stale NFS
> Filehandle" and "Permission Denied" errors on machines mounting the
> shares provided by the two PC's. Very sporadic, but annoying.
>
> I can't seem to find any rhyme or reason for this. Clients that have
> seen the problem include a machine running RH 7.3 accessing a mount in
> fstab, to a Fedora Core 1 client automounting a share. Many times just
> running 'ls' on the share a few times will suddenly make it accessable.
> Other times a umount/mount is required.
>
> The server machines are running Fedora Core 2 and kernel
> 2.6.9-1.3_FC2smp. The exported filesystems are ReiserFS on LVM2
> volumes. Qlogic QLA2300 fibre adaptors connect the heads to the Nexsan
> Atabeast.
>
> After reading some traffic on the Linux kernel list, I added the
> "no_subtree_check" option to the fstab entries on the servers and
> re-exported. It doesn't seem to have made much of a difference.
>
> I'm not seeing error messages in /var/log/messages on either the clients
> nor the hosts.
>
> Anyone else seeing this? Any ideas? Otherwise the performance on the
> new systems beats the hell out of our old EMC Celerra; the users are
> rather happy with it save for this little problem.
>
> Hugh
>
--
Michael Haverkamp
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2004-11-23 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 1:18 Stale NFS Filehandles and Permission Denied on 2.6.9 Hugh Caley
2004-11-23 14:06 ` Michael Haverkamp [this message]
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=41A343C8.7090106@kcp.com \
--to=mhaverkamp@kcp.com \
--cc=Hugh_Caley@affymetrix.com \
--cc=nfs@lists.sourceforge.net \
/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