From: Vaclav Stepan <w@linux.fjfi.cvut.cz>
To: NFS mailing list <nfs@lists.sourceforge.net>
Subject: fh_verify: no squashed_root access at session/lastsession (2.4.23 knfsd and Solaris 9)
Date: Wed, 10 Dec 2003 17:25:54 +0100 [thread overview]
Message-ID: <1071073554.1392.15.camel@tp> (raw)
Hello,
we ran in trouble while upgrading from 2.4.20pre1 to 2.4.23 kernel
on a GNU/Linux box which serves two Solaris 9 clients and one Linux
client.
When the export get set up and some mount attempt comes, the server
starts flooding the logs and screen with:
fh_verify: no root_squashed access at session/lastsession
(several messages per second). The server doesn't panic or crash --- I
am able to shut down knfsd without any harm --- everything works, just
the NFS drives are inaccessible.
There is a workaround using no_subtree_check as an option in the exports
file, but can anyone help me explain this? I found only two relevant
posts using Google with "fh_verify root_squashed" as keywords:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=110421
http://www.ussg.iu.edu/hypermail/linux/kernel/0309.1/1159.html
Thanks for your time
Vaclav Stepan
--
Vaclav Stepan
w@linux.fjfi.cvut.cz
http://linux.fjfi.cvut.cz/~w/
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2003-12-10 16:41 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=1071073554.1392.15.camel@tp \
--to=w@linux.fjfi.cvut.cz \
--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