lkml.org 
[lkml]   [2002]   [Jan]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [NFS] some strangeness (at least) with linux-2.4.17-NFS_ALL patch
From
>>>>> " " == Hans-Peter Jansen <hpj@urpla.net> writes:
>> What server is this?
> Oups, sorry:
> Linux shrek 2.4.13-ac7 #6 SMP Son Dez 2 20:02:04 CET 2001 i686 unknown
> (on patches, IIRC)

And the knfsd server daemons (not the user-space 'unfsd')?

> Shouldn't the client invalidate the dcache entry some time?
> Now, 5 hours later, the dcache entry isn't invalidated, yet.

5 hours??? Unless you have set some crazy value for acdirmax, then it
should indeed have been revalidated under normal circumstances.

The default is for all attribute/dcache entries to time out at least
once every 60 seconds. That is what happens on my test setup at least.

> I think, this is a thinko.

It shouldn't be. There might be a bug lingering somewhere, but
revalidation *is* normally supposed to occur.

Are you sure that you didn't mess up the fixups with 2.4.18-pre1? That
might explain things, since you would be messing with
nfs_refresh_inode. What you need to do against 2.4.18-pre1 is first to
revert the patch linux-2.4.17-fattr.dif. After that you should be able
to apply linux-2.4.17-NFS_ALL.dif directly without any rejections...

> Please try this:

> shrek is the server, elfe the client /raid is shared (reiserfs,
> no raid), /tmp isn't

<snip>

> Eingabe-/Ausgabefehler insgesamt 1 drwxr-xr-x 2 root root 55
> 11. Jan 20:08 ./ drwxr-xr-x 9 root root 218 11. Jan 20:06 ../

> Pretty simple. Can you reproduce this?

Nope. With /mnt/trondmy == NFS share, /tmp == local:

[trondmy@fyspc-epf03 gnurr]$ pwd
/mnt/trondmy/gnurr
[trondmy@fyspc-epf03 gnurr]$ touch /tmp/huhu
[trondmy@fyspc-epf03 gnurr]$ ln -s /tmp/huhu
[trondmy@fyspc-epf03 gnurr]$ ls -al
totalt 8
drwxr-xr-x 2 trondmy trondmy 4096 jan 12 02:43 .
drwxr-xr-x 41 trondmy trondmy 4096 jan 12 02:42 ..
lrwxrwxrwx 1 trondmy trondmy 9 jan 12 02:43 huhu ->
/tmp/huhu
[trondmy@fyspc-epf03 gnurr]$ echo "huhu" > /tmp/huhu
[trondmy@fyspc-epf03 gnurr]$ ls -al
totalt 8
drwxr-xr-x 2 trondmy trondmy 4096 jan 12 02:43 .
drwxr-xr-x 41 trondmy trondmy 4096 jan 12 02:42 ..
lrwxrwxrwx 1 trondmy trondmy 9 jan 12 02:43 huhu ->
/tmp/huhu
[trondmy@fyspc-epf03 gnurr]$ cat huhu
huhu
[trondmy@fyspc-epf03 gnurr]$ rm huhu
[trondmy@fyspc-epf03 gnurr]$ ls -al
totalt 8
drwxr-xr-x 2 trondmy trondmy 4096 jan 12 02:44 .
drwxr-xr-x 41 trondmy trondmy 4096 jan 12 02:42 ..
[trondmy@fyspc-epf03 gnurr]$ touch huhu
[trondmy@fyspc-epf03 gnurr]$ ls -al
totalt 8
drwxr-xr-x 2 trondmy trondmy 4096 jan 12 02:44 .
drwxr-xr-x 41 trondmy trondmy 4096 jan 12 02:42 ..
-rw-r--r-- 1 trondmy trondmy 0 jan 12 02:44 huhu

Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:15    [W:0.115 / U:1.848 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site