From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs3/krb5 mounts fail
Date: Tue, 12 Dec 2006 23:38:49 -0500 [thread overview]
Message-ID: <20061213043848.GA23539@fieldses.org> (raw)
In-Reply-To: <4d569c330612121817u715a0ad2g10b2f7a46a4a26fe@mail.gmail.com>
On Tue, Dec 12, 2006 at 09:17:43PM -0500, Kevin Coffman wrote:
> I believe this looks exactly like the problem discussed here:
> http://marc.theaimsgroup.com/?l=linux-nfs&m=116225377701186&w=2
>
> I don't recall coming up with a solution. The theory was possibly a
> memory leak.
I don't know.
> Bruce, could this be related to the leaks recently discovered and plugged?
There'd be no harm in trying a kernel with those bugs fixed:
http://www.citi.umich.edu/projects/nfsv4/linux/kernel-patches/2.6.19-rc6-1/linux-2.6.19-rc6-CITI_NFS4_ALL-1.diff
But I don't think any of those bugs would explain this.
--b.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-12-13 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 18:55 nfs3/krb5 mounts fail Christian G. Warden
2006-12-12 17:20 ` Kevin Coffman
2006-12-12 23:38 ` Christian G. Warden
2006-12-13 2:07 ` Kevin Coffman
2006-12-13 2:17 ` Kevin Coffman
2006-12-13 4:38 ` J. Bruce Fields [this message]
2006-12-14 23:04 ` Christian G. Warden
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=20061213043848.GA23539@fieldses.org \
--to=bfields@fieldses.org \
--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