From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: [BUG] All Kerberos mounts stop working, restarting rpc.svcgssd helps
Date: Fri, 3 Nov 2006 13:37:37 +0100 [thread overview]
Message-ID: <20061103123737.GA5199@uio.no> (raw)
In-Reply-To: <20061031143248.GA8444@uio.no>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
On Tue, Oct 31, 2006 at 03:32:48PM +0100, Steinar H. Gunderson wrote:
> Data is no longer available on those existing mounts. In fact, if I run ls
> -ld on the mount point, it is suddenly owned by the user and group "?".
I figured out later that this isn't always true -- for instance, in one case
root could ls a directory, but others couldn't (and new mounts wouldn't
work).
>> Could you send a packet trace from the server after mounts stop
>> working? (tcpdump -s 0 -w /tmp/x) Also, if it is enabled, could you
>> get the output from sysRq-T?
> I'll be sure to grab the data next time the problems occur.
Here we go. The dump is a complete tcpdump from the server (129.241.93.19) at
the same time as a client (129.241.93.50) attempts to do a "mount -t nfs4 -o
sec=krb5i cassarossa:/itk /mnt". The call traces is the result of a "cat
/proc/kmsg" while running "echo t > /proc/sysrq-trigger".
/* Steinar */
--
Homepage: http://www.sesse.net/
[-- Attachment #2: svcgssd-not-working.calltraces.bz2 --]
[-- Type: application/octet-stream, Size: 31667 bytes --]
[-- Attachment #3: svcgssd-not-working.dump.bz2 --]
[-- Type: application/octet-stream, Size: 19704 bytes --]
[-- Attachment #4: Type: text/plain, Size: 373 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #5: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-11-03 12:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 0:12 [BUG] All Kerberos mounts stop working, restarting rpc.svcgssd helps Steinar H. Gunderson
2006-10-31 4:53 ` Kevin Coffman
2006-10-31 10:03 ` Steinar H. Gunderson
2006-10-31 13:43 ` Kevin Coffman
2006-10-31 14:32 ` Steinar H. Gunderson
2006-11-03 12:37 ` Steinar H. Gunderson [this message]
2006-11-06 23:08 ` Kevin Coffman
2006-11-06 23:15 ` J. Bruce Fields
2006-11-06 23:16 ` Steinar H. Gunderson
2006-11-06 23:18 ` J. Bruce Fields
2006-11-06 23:22 ` J. Bruce Fields
2006-11-06 23:46 ` Steinar H. Gunderson
2006-11-06 23:49 ` J. Bruce Fields
2006-11-07 0:47 ` Steinar H. Gunderson
2006-11-08 0:44 ` J. Bruce Fields
2006-11-08 0:50 ` Steinar H. Gunderson
2006-11-10 20:11 ` Kevin Coffman
2006-11-10 20:25 ` J. Bruce Fields
2006-11-10 20:39 ` Kevin Coffman
2006-11-10 20:49 ` J. Bruce Fields
2006-11-10 21:37 ` Kevin Coffman
2006-11-10 21:41 ` J. Bruce Fields
2006-11-10 21:43 ` Kevin Coffman
2006-11-06 23:44 ` Steinar H. Gunderson
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=20061103123737.GA5199@uio.no \
--to=sgunderson@bigfoot.com \
--cc=kwc@citi.umich.edu \
--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