From: Andi Kleen <ak@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: okir@suse.de, linux-kernel@vger.kernel.org
Subject: Re: radix-tree.c:378 BUG NFS client bug on 2.6.15-git7
Date: Tue, 7 Feb 2006 15:04:18 +0100 [thread overview]
Message-ID: <200602071504.18997.ak@suse.de> (raw)
In-Reply-To: <1139320822.7864.3.camel@lade.trondhjem.org>
On Tuesday 07 February 2006 15:00, Trond Myklebust wrote:
> On Tue, 2006-02-07 at 11:46 +0100, Andi Kleen wrote:
> > Found this on a box still running 2.6.15-git7 (I know it's a bit old).
> > It was under relatively heavy NFS client traffic. Perhaps it's of interest
> > for someone.
> >
> > -Andi
> >
> >
> > nfs_update_inode: inode 961647 mode changed, 0040755 to 0100644
>
> This is weird. The server appears to have magically changed a directory
> into a regular file...
>
> Would this be the userland server or is it knfsd?
Could be either. The machine is in a complex automount setup
which includes both types of servers. And both should be regularly
accessed.
-Andi
prev parent reply other threads:[~2006-02-07 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 10:46 radix-tree.c:378 BUG NFS client bug on 2.6.15-git7 Andi Kleen
2006-02-07 14:00 ` Trond Myklebust
2006-02-07 14:04 ` Andi Kleen [this message]
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=200602071504.18997.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=okir@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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