From: Jan Kasprzak <kas@informatics.muni.cz>
To: linux-kernel@vger.kernel.org
Subject: 2.6 NFS stale filehandle with subtree_check
Date: Thu, 15 Jan 2004 14:14:55 +0100 [thread overview]
Message-ID: <20040115141454.B17239@fi.muni.cz> (raw)
Hello all,
I have a NFS fileserver (currently based on XFS on 3ware RAID),
which I have tried to upgrade to 2.6. kernel. After reboot, clients
started to see partial directories, or cannot open/create files in
their cwd, with the "stale NFS file handle" message. Using no_subtree_check
option in /etc/exports helped, as well as going back to 2.4+XFS.
It is probably not XFS related, because I had the same problem
on an older HW of this server (which had an ext3 volumes on software RAID)
and some 2.6.0-pre kernel. At that time I did not know that I had to try
no_subtree_check, so I don't know whether this would have fixed the
problem on the older HW. I went back to 2.4 then.
The machine serves the home directories via NFS and Samba.
I have home directories for ~2200 users there, each one with its own
/etc/exports entry[1]. NFS clients are various Linux, Solaris and IRIX
workstations and servers.
Is it possible to use subtree_check in NFS in 2.6? Thanks,
-Yenya
[1] For another unrelated user-space problem with such a big /etc/exports,
see http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=76643
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Czech Linux Homepage: http://www.linux.cz/ |
| I actually have a lot of admiration and respect for the PATA knowledge |
| embedded in drivers/ide. But I would never call it pretty:) -Jeff Garzik |
reply other threads:[~2004-01-15 13:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040115141454.B17239@fi.muni.cz \
--to=kas@informatics.muni.cz \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®