From: Pawel Dziekonski <pawel.dziekonski@pwr.wroc.pl>
To: linux-kernel@vger.kernel.org
Subject: 2.4.22-ac1 -- fh_verify: no root_squashed access at ...
Date: Thu, 11 Sep 2003 09:35:34 +0200 [thread overview]
Message-ID: <20030911073534.GA5534@pwr.wroc.pl> (raw)
Hi,
instantly after switching from 2.4.21-pre6 to 2.4.22-ac1 I get loads of
that in logs:
fh_verify: no root_squashed access at my-dir
where my-dir is a subdirectory of parent which is exported to
several machines, and is also remounted locally for some reason ;-)
what has changed?
thanks in advence, Pawel
--
Pawel Dziekonski <pawel.dziekonski|@|pwr.wroc.pl>, KDM WCSS avatar:0:0:
Wroclaw Networking & Supercomputing Center, HPC Department
-> See message headers for privacy policy info.
reply other threads:[~2003-09-11 7:35 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=20030911073534.GA5534@pwr.wroc.pl \
--to=pawel.dziekonski@pwr.wroc.pl \
--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