From: Andrew Gray <grayaw@egr.unlv.edu>
To: linux-kernel@vger.kernel.org
Subject: fh_verify: no root_squashed access hundreds of times a second again
Date: Fri, 13 Feb 2004 09:18:32 -0800 [thread overview]
Message-ID: <1076692518.15751.5.camel@blargh> (raw)
I'm not subscribed to the linux-kernel list, I would appreciate a CC on
any replies, but I will be watching the list as well. I'm reposting
this message in the hope someone will answer - neither I nor the mailing
list got any replies last time.
I am using kernel 2.4.24 on a heavily-used NFS server. I am receiving
hundreds of messages like:
"kernel: fh_verify: no root_squashed access at sessions/lastsession."
in my messages log, usually accompanied by a "last message repeated 6497
times" a minute or so later. I'm gathering it is just reporting it is
denying root access to a share, which is fine and exactly what I asked
for. Is there anyway to shut this logging off without just wiping the
line from fs/nfsd/nfsfh.c? I really can't afford to be rebooting the box
to install a new kernel right now. I've searched google, linux-kernel,
and other resources, and while I've found others with the same problem,
no solutions have been posted.
--
Andrew Gray
Systems Administrator
College of Engineering
University of Nevada, Las Vegas
next reply other threads:[~2004-02-13 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 17:18 Andrew Gray [this message]
2004-02-14 16:02 ` fh_verify: no root_squashed access hundreds of times a second again Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 19:27 Andrew Gray
2004-02-18 0:02 Andrew Gray
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=1076692518.15751.5.camel@blargh \
--to=grayaw@egr.unlv.edu \
--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