From: linuxkernel@arcor.de
To: nfs@lists.sourceforge.net
Subject: Re: several oopses of nfsd in 2.6.16.29
Date: Fri, 1 Dec 2006 11:59:13 +0100 (CET) [thread overview]
Message-ID: <3606592.1164970753868.JavaMail.ngmail@webmail13> (raw)
In-Reply-To: 139134.1164970331572.JavaMail.ngmail@webmail13
(forgot to cc to the list)
----- Original Nachricht ----
Von: linuxkernel@arcor.de
An: okir@suse.de
Datum: 01.12.2006 11:52
Betreff: Re: [NFS] several oopses of nfsd in 2.6.16.29
Hello,
thanks for your reply!
> On Fri, Dec 01, 2006 at 09:06:35AM +0100, linuxkernel@arcor.de wrote:
> > it happened again, but this time without /proc/fs/nfsd mounted. This is
> getting on my nerves.
> > Please see attached the oopses. Now I switched to 2.6.16.33.
>
> It doesn't look like this is necessarily nfsd's fault; this looks more
ok, I only saw "Process: nfsd" in the oops, that's why I report it here.
> like memory corruption to me. Something stomped on either the inode or
> (less likely) the inode->ops of some file.
possible but oopses also occured on the other machine, although
they weren't logged, but okay I'll run a memtest. And the filesystems
of these machines are synced via rsync, not via drbd, so the inodes
are different.
>
> I'd suggest building the kernel with slab debugging enabled and
> see whether that turns up anything useful.
do I have to do anything special besides building with CONFIG_DEBUG_SLAB?
>
> There's a remote chance this is related to ACLs though, as the
> first crash is in an ACL call. Are you using ACLs at all?
yes, they are mounted with acl, but it is not used at the moment,
I don't even think there is any file with acls set.
Thanks again,
Peter
-------------------------------------------------------------------------
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 parent reply other threads:[~2006-12-01 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <139134.1164970331572.JavaMail.ngmail@webmail13>
2006-12-01 10:59 ` linuxkernel [this message]
2006-12-06 5:33 several oopses of nfsd in 2.6.16.29 Kevin Jamieson
-- strict thread matches above, loose matches on Subject: below --
2006-12-01 8:06 linuxkernel
2006-12-01 9:26 ` Olaf Kirch
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=3606592.1164970753868.JavaMail.ngmail@webmail13 \
--to=linuxkernel@arcor.de \
--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