From: Chip Salzenberg <chip@pobox.com>
To: nfs@lists.sourceforge.net
Subject: More user reports: '{Random,Consistent} mount refusals'
Date: Sun, 15 Sep 2002 18:09:53 -0400 [thread overview]
Message-ID: <20020915220953.GD11002@perlsupport.com> (raw)
I really don't know what to make of Debian bugs 81428 and 131811:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81428&repeatmerged=yes
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=131811&repeatmerged=yes
Here is the most recent message from 81428. Please help me figure out
what's going on here ... I'm mostly packaging and mostly not coding in
NFS land, and these reports are awfully confusing.
----- Forwarded message from Adam C Powell IV <hazelsct@mit.edu> -----
Subject: Bug#81428: I'm still getting random mount refusals
From: Adam C Powell IV <hazelsct@mit.edu>
Date: Tue, 15 Jan 2002 09:58:39 -0500
Even with 1.0-2 on a 2.4.9 kernel which I rebooted yesterday, I'm still
getting this problem. For a while I thought it was just a matter of
being slow to respond to changes in /etc/exports (like, I make a change,
but it doesn't take, then suddenly a few days later without restarting
the server, it magically works and I can mount). I often try testing
every day after a change, and it takes somewhere between five and eight
days for the change to take effect. This goes both for netgroup,
wildcard (*.domain.edu) and individual machine type entries in
/etc/exports, for clients in /etc/hosts.
Last night, the server crashed (no idea why), so I rebooted, and
remounted one of the dirs on the client machines while the server was
still fscking it, so the fs was not mounted on the server, and the dir
was empty. When the fsck was done and the dir mounted on the server,
"ls /dir" on the client still showed it empty. This morning, I tried to
unmount and remount, but got:
mount: <server>:/dir failed, reason given by server: Permission denied
Here's /var/log/messages on the server for this unmount-mount:
Jan 15 09:35:44 <server> rpc.mountd: authenticated unmount request from
<client.domain.edu>:702 for /dir (/dir)
Jan 15 09:35:46 <server> rpc.mountd: authenticated mount request from
<client.domain.edu>:703 for /dir (/dir)
Jan 15 09:35:46 <server> rpc.mountd: getfh failed: Operation not permitted
It's possible that kernels newer than 2.4.9 have fixed this, but 2.4.14
through 2.4.17 have been misidentifying my disk labels (I'm about to
file a bug), so I can't test them on that server.
This bug is *so* annoying, I can't tell you, and has been since about
the time this bug was submitted. Please don't close this until you know
for certain it is fixed - until the submitter or (if you can't reach
him/her) I confirms that it's fixed. I really hope it gets fixed before
the woody release!
Zeen,
--
-Adam P.
GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6
Welcome to the best software in the world today cafe!
<http://lyre.mit.edu/%7Epowell/The_Best_Stuff_In_The_World_Today_Cafe.ogg>
----- End forwarded message -----
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"It furthers one to have somewhere to go."
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-09-15 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 22:09 Chip Salzenberg [this message]
2002-09-15 22:40 ` More user reports: '{Random,Consistent} mount refusals' Neil Brown
2002-09-15 22:46 ` Neil Brown
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=20020915220953.GD11002@perlsupport.com \
--to=chip@pobox.com \
--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