Hello Trond, hello all,
can you explain what this means:
kernel: nfsd-fh: found a name that I didn't expect: <filename>
Should something be done against it, or is it simply informative?
Comes up on 2.4.20 kernel based nfs-server quite often. Exported FS is reiserfs
sized about 500 GB.
--
Regards,
Stephan
>>>>> " " == Stephan von Krawczynski <[email protected]> writes:
> Hello Trond, hello all, can you explain what this means:
> kernel: nfsd-fh: found a name that I didn't expect: <filename>
> Should something be done against it, or is it simply
> informative?
The comment in the code just above the printk() reads
/* Now that IS odd. I wonder what it means... */
Looks like you and Neil (and possibly the ReiserFS team) might want to
have a chat...
Cheers,
Trond
On Tue, 18 Mar 2003 16:31:43 +0100
Trond Myklebust <[email protected]> wrote:
> >>>>> " " == Stephan von Krawczynski <[email protected]> writes:
>
> > Hello Trond, hello all, can you explain what this means:
>
> > kernel: nfsd-fh: found a name that I didn't expect: <filename>
>
> > Should something be done against it, or is it simply
> > informative?
>
> The comment in the code just above the printk() reads
>
> /* Now that IS odd. I wonder what it means... */
>
> Looks like you and Neil (and possibly the ReiserFS team) might want to
> have a chat...
I'm all for it. Who has a glue? I have in fact tons of these messages, it's a
pretty large nfs server.
--
Regards,
Stephan
Hello!
On Tue, Mar 18, 2003 at 04:42:04PM +0100, Stephan von Krawczynski wrote:
> > The comment in the code just above the printk() reads
> > /* Now that IS odd. I wonder what it means... */
> > Looks like you and Neil (and possibly the ReiserFS team) might want to
> > have a chat...
> I'm all for it. Who has a glue? I have in fact tons of these messages, it's a
> pretty large nfs server.
What is the typical usage pattern for files whose names are printed?
Are they created/deleted often by multiple clients/processes by any chance?
Bye,
Oleg
On Tue, 18 Mar 2003 19:07:33 +0300
Oleg Drokin <[email protected]> wrote:
> Hello!
>
> On Tue, Mar 18, 2003 at 04:42:04PM +0100, Stephan von Krawczynski wrote:
>
> > > The comment in the code just above the printk() reads
> > > /* Now that IS odd. I wonder what it means... */
> > > Looks like you and Neil (and possibly the ReiserFS team) might want to
> > > have a chat...
> > I'm all for it. Who has a glue? I have in fact tons of these messages, it's
> > a pretty large nfs server.
>
> What is the typical usage pattern for files whose names are printed?
> Are they created/deleted often by multiple clients/processes by any chance?
This is a nfs-server who serves web-servers (apache). I find a lot of these
messages, but they (upto now) only point to 3 different filenames. And these
are in fact all directories. The box never crashed and has currently 20 days
uptime. It is dual P-III and has 6 GB of RAM.
The questionable directories were created long before they first showed this
message and have never changed (regarding name-change). Their contents were
possible changed but surely not often meaning no more than once a day or once a
week.
It may well occur that multiple nfs-client systems _read_ them, as well as
multiple processes on one client.
The nfs-clients are 2.4.19 boxes and one 2.2.21.
--
Regards,
Stephan
On Tue, 18 Mar 2003 17:41:06 +0100
Stephan von Krawczynski <[email protected]> wrote:
> On Tue, 18 Mar 2003 17:28:25 +0100
> Stephan von Krawczynski <[email protected]> wrote:
>
> > On Tue, 18 Mar 2003 19:07:33 +0300
> > Oleg Drokin <[email protected]> wrote:
> >
> > > Hello!
> > >
> > > On Tue, Mar 18, 2003 at 04:42:04PM +0100, Stephan von Krawczynski wrote:
> > >
> > > > > The comment in the code just above the printk() reads
> > > > > /* Now that IS odd. I wonder what it means... */
> > > > > Looks like you and Neil (and possibly the ReiserFS team) might want to
> > > > > have a chat...
> > > > I'm all for it. Who has a glue? I have in fact tons of these messages, it's
> > > > a pretty large nfs server.
> > >
> > > What is the typical usage pattern for files whose names are printed?
> > > Are they created/deleted often by multiple clients/processes by any chance?
> >
> > This is a nfs-server who serves web-servers (apache). I find a lot of these
> > messages, but they (upto now) only point to 3 different filenames. And these
> > are in fact all directories. The box never crashed and has currently 20 days
> > uptime. It is dual P-III and has 6 GB of RAM.
> > The questionable directories were created long before they first showed this
> > message and have never changed (regarding name-change). Their contents were
> > possible changed but surely not often meaning no more than once a day or once a
> > week.
> > It may well occur that multiple nfs-client systems _read_ them, as well as
> > multiple processes on one client.
> > The nfs-clients are 2.4.19 boxes and one 2.2.21.
>
> And one addition:
> They are all second level, meaning look like:
Please ignore this rather silly comment. One should read code before commenting ;-)
--
Regards,
Stephan
On Tue, 18 Mar 2003 17:28:25 +0100
Stephan von Krawczynski <[email protected]> wrote:
> On Tue, 18 Mar 2003 19:07:33 +0300
> Oleg Drokin <[email protected]> wrote:
>
> > Hello!
> >
> > On Tue, Mar 18, 2003 at 04:42:04PM +0100, Stephan von Krawczynski wrote:
> >
> > > > The comment in the code just above the printk() reads
> > > > /* Now that IS odd. I wonder what it means... */
> > > > Looks like you and Neil (and possibly the ReiserFS team) might want to
> > > > have a chat...
> > > I'm all for it. Who has a glue? I have in fact tons of these messages, it's
> > > a pretty large nfs server.
> >
> > What is the typical usage pattern for files whose names are printed?
> > Are they created/deleted often by multiple clients/processes by any chance?
>
> This is a nfs-server who serves web-servers (apache). I find a lot of these
> messages, but they (upto now) only point to 3 different filenames. And these
> are in fact all directories. The box never crashed and has currently 20 days
> uptime. It is dual P-III and has 6 GB of RAM.
> The questionable directories were created long before they first showed this
> message and have never changed (regarding name-change). Their contents were
> possible changed but surely not often meaning no more than once a day or once a
> week.
> It may well occur that multiple nfs-client systems _read_ them, as well as
> multiple processes on one client.
> The nfs-clients are 2.4.19 boxes and one 2.2.21.
And one addition:
They are all second level, meaning look like:
kernel: nfsd-fh: found a name that I didn't expect: libyen2000/pics
(where pics is a directory, too)
--
Regards,
Stephan
On Tuesday 18 March 2003 17:07, Oleg Drokin wrote:
> Hello!
>
> On Tue, Mar 18, 2003 at 04:42:04PM +0100, Stephan von Krawczynski wrote:
> > > The comment in the code just above the printk() reads
> > > /* Now that IS odd. I wonder what it means... */
> > > Looks like you and Neil (and possibly the ReiserFS team) might want to
> > > have a chat...
> >
> > I'm all for it. Who has a glue? I have in fact tons of these messages,
> > it's a pretty large nfs server.
>
> What is the typical usage pattern for files whose names are printed?
> Are they created/deleted often by multiple clients/processes by any chance?
>
Hi,
we also sometimes see those messages. In our case it seems to appears rather
often for the local/share/perl directory of our /usr/local directory:
nfsd-fh: found a name that I didn't expect: share/perl
This directory is certainly never deleted when this message appears, actually
data are very, very seldem written to it.
Once this message also appeared for a file:
servicetypes/kdeveloplanguagesupport.desktop
I can't tell you how often kde deletes this file.
Please ask if you need more information.
Bernd
On Tuesday March 18, [email protected] wrote:
> On Tue, 18 Mar 2003 16:31:43 +0100
> Trond Myklebust <[email protected]> wrote:
>
> > >>>>> " " == Stephan von Krawczynski <[email protected]> writes:
> >
> > > Hello Trond, hello all, can you explain what this means:
> >
> > > kernel: nfsd-fh: found a name that I didn't expect: <filename>
> >
> > > Should something be done against it, or is it simply
> > > informative?
> >
> > The comment in the code just above the printk() reads
> >
> > /* Now that IS odd. I wonder what it means... */
> >
> > Looks like you and Neil (and possibly the ReiserFS team) might want to
> > have a chat...
>
> I'm all for it. Who has a glue? I have in fact tons of these messages, it's a
> pretty large nfs server.
When knfsd gets a request for a filehandle which refers to an object
that isn't in the dcache, it needs to get it into the dcache. This
involves finding it's name and splicing it in.
It gets hold of an inode for the parent directory (don't worry how)
and reads through that directory looking for a name with the right
inode number. When it finds the name, it checks to see that the name
isn't already in the dcache under that directory. As the object with
that name isn't in the dcache you would expect the name not to be
their either. This message indicates that the name was there.
I think there is enough locking in place so that a race between one
process adding the name and another process looking up the name for an
object should not stumble over each other - both hold i_sem for the
directory. So I don't think that would be the cause.
Maybe this is reiserfs specific. Has anyone seen it on a non-reiserfs
filesystem? Possibly reiserfs does something funny with inode numbers
that is confusing the name lookup.
If it doesn't seem to correlate with other symptoms, I probably
wouldn't worry about it.
2.5 does all this quite differently so shouldn't have the same problem
(it certainly doesn't contain the same error message).
NeilBrown
Hello!
On Tue, Mar 18, 2003 at 06:28:59PM +0100, Bernd Schubert wrote:
> we also sometimes see those messages. In our case it seems to appears rather
> often for the local/share/perl directory of our /usr/local directory:
> nfsd-fh: found a name that I didn't expect: share/perl
Do you also use reiserfs for your /usr/local filesystem?
Bye,
Oleg
On Wed, 19 Mar 2003 09:09:49 +1100
Neil Brown <[email protected]> wrote:
> Maybe this is reiserfs specific. Has anyone seen it on a non-reiserfs
> filesystem? Possibly reiserfs does something funny with inode numbers
> that is confusing the name lookup.
>
> If it doesn't seem to correlate with other symptoms, I probably
> wouldn't worry about it.
I re-checked the logfile and it looks like the read request (or open request)
is in fact failing, so something should be done. The apache-log looks like:
[Mon Mar 17 22:55:56 2003] [crit] [client w.x.y.z] (17)File exists: /a/b/c/d/e
pcfg_openfile: unable to check htaccess file, ensure it is readable
The corresponding nfs message is:
Mar 17 22:55:55 me kernel: nfsd-fh: found a name that I didn't expect: c/d
--
Regards,
Stephan
On Wednesday 19 March 2003 07:43, Oleg Drokin wrote:
> Hello!
>
> On Tue, Mar 18, 2003 at 06:28:59PM +0100, Bernd Schubert wrote:
> > we also sometimes see those messages. In our case it seems to appears
> > rather often for the local/share/perl directory of our /usr/local
> > directory: nfsd-fh: found a name that I didn't expect: share/perl
>
> Do you also use reiserfs for your /usr/local filesystem?
>
Yes of course, otherwise I wouldn't have replied to this thread.
Best regards,
Bernd