From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [NFS] some strangeness (at least) with linux-2.4.17-NFS_ALL patch
Date: Sat, 12 Jan 2002 03:04:32 +0100 [thread overview]
Message-ID: <15423.39344.864108.741338@charged.uio.no> (raw)
In-Reply-To: <20020111191744.7A9CE1426@shrek.lisa.de>
In-Reply-To: <20020111131528.44F8613E6@shrek.lisa.de> <15422.65459.871735.203004@charged.uio.no> <20020111191744.7A9CE1426@shrek.lisa.de>
>>>>> " " == 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
prev parent reply other threads:[~2002-01-12 2:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 13:15 Hans-Peter Jansen
2002-01-11 15:07 ` Trond Myklebust
2002-01-11 19:17 ` Hans-Peter Jansen
2002-01-12 2:24 ` Trond Myklebust
2002-01-12 17:01 ` [NFS] some strangeness (at least) with linux-2.4.18-NFS_ALL patch Hans-Peter Jansen
2002-01-12 18:47 ` Trond Myklebust
2002-01-12 22:40 ` Hans-Peter Jansen
2002-01-13 12:37 ` Trond Myklebust
2002-01-12 2:04 ` Trond Myklebust [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=15423.39344.864108.741338@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=hpj@urpla.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®