From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jakob Østergaard <jakob@unthought.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stale NFS handles on 2.4.1
Date: 14 Feb 2001 01:02:05 +0100 [thread overview]
Message-ID: <shsitme169u.fsf@charged.uio.no> (raw)
In-Reply-To: <20010214002750.B11906@unthought.net>
In-Reply-To: Jakob Østergaard's message of "Wed, 14 Feb 2001 00:27:50 +0100"
>>>>> " " == stergaard <Jakob> writes:
> What happens is that one machine will finish compiling, and
> another machine will immediately thereafter do a "touch
> some_output.o". This "touch" sometimes fails with a stale
> handle message.
Does the appended patch change anything?
Cheers,
Trond
--- linux-2.4.1/fs/nfs/inode.c.orig Tue Dec 12 02:46:04 2000
+++ linux-2.4.1/fs/nfs/inode.c Wed Feb 14 01:00:33 2001
@@ -100,6 +100,7 @@
inode->i_rdev = 0;
NFS_FILEID(inode) = 0;
NFS_FSID(inode) = 0;
+ NFS_FLAGS(inode) = 0;
INIT_LIST_HEAD(&inode->u.nfs_i.read);
INIT_LIST_HEAD(&inode->u.nfs_i.dirty);
INIT_LIST_HEAD(&inode->u.nfs_i.commit);
next prev parent reply other threads:[~2001-02-14 0:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 23:27 Stale NFS handles on 2.4.1 Jakob Østergaard
2001-02-13 23:31 ` Alan Cox
2001-02-13 23:43 ` Jakob Østergaard
2001-02-14 8:35 ` Rogier Wolff
2001-02-14 0:02 ` Trond Myklebust [this message]
2001-02-24 20:18 ` Stale NFS handles on 2.4.2 David Fries
2001-02-25 5:43 ` Neil Brown
2001-02-25 5:53 ` David Fries
2001-02-25 9:25 ` Neil Brown
2001-02-25 19:10 ` David Fries
2001-02-28 0:12 ` Neil Brown
2001-02-28 12:02 ` Trond Myklebust
2001-02-28 22:15 ` Neil Brown
2001-03-01 1:13 ` Trond Myklebust
[not found] ` <20010228211808.C24668@d-131-151-189-65.dynamic.umr.edu>
2001-03-01 9:07 ` Trond Myklebust
[not found] ` <s5gwva9simp.fsf@egghead.curl.com>
2001-03-01 14:13 ` Stale NFS handles on 2.4.2^H^H^H^H^H2.2.19 Trond Myklebust
2001-02-25 14:00 ` Stale NFS handles on 2.4.2 Trond Myklebust
2001-02-26 9:54 ` Lennert Buytenhek
2001-02-26 15:56 ` David Fries
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=shsitme169u.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=jakob@unthought.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