From: Marc Schmitt <mschmitt@inf.ethz.ch>
Cc: nfs@lists.sourceforge.net
Subject: Re: rpc.mountd: getfh failed: Operation not permitted
Date: Tue, 19 Aug 2003 16:50:48 +0200 [thread overview]
Message-ID: <3F423948.9090204@inf.ethz.ch> (raw)
In-Reply-To: <3F3119E5.2040207@inf.ethz.ch>
Marc Schmitt wrote:
> - upgrade to kernel >= 2.4.20 (which is something I have to do tonight
> anyway, the server currently suffers from the quota bug in 2.4.18-27
> that was solved in 2.4.20-18, too: "kernel: VFS: find_free_dqentry():
> Data block full but it shouldn't. kernel: VFS: Error -5 occured while
> creating quota.")
:(
The upgrade to kernel 2.4.20-19 did not help, today again, I had to
restart the NFS service due to the "getfh failed: Operation not
permitted." error.
I've compared the logs (Aug 4th and today). What is interesting is that
the VFS quota error appeared again today, too. The quota bug occured
first at 6am and continued happening about once an hour till 11:45am.
45' later, the first getfh error appears in the logs. Short after that,
I've restarted the NFS service.
I'd love to help debugging this problem. I'd appreciate some pointers
where to start, though. How can I provide debugging infos while still
keeping the machine in production?
What I may try is running vanilla kernel 2.4.22 (once it's out), too, I
saw that there are improvements for machines with heavy I/O load.
TIA
Regards,
Marc
-------------------------------------------------------
This SF.net email is sponsored by Dice.com.
Did you know that Dice has over 25,000 tech jobs available today? From
careers in IT to Engineering to Tech Sales, Dice has tech jobs from the
best hiring companies. http://www.dice.com/index.epl?rel_code=104
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-08-19 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 15:08 rpc.mountd: getfh failed: Operation not permitted Marc Schmitt
2003-08-19 14:50 ` Marc Schmitt [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-23 13:26 James Pearson
2005-02-01 23:03 jehan.procaccia
2005-02-02 14:02 ` Steve Dickson
[not found] <20050203041550.746BD89D13@sc8-sf-spam1.sourceforge.net>
2005-02-03 17:52 ` Jos van Wezel
2005-02-03 19:40 ` Steve Dickson
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=3F423948.9090204@inf.ethz.ch \
--to=mschmitt@inf.ethz.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.