From: Mike Fedyk <mfedyk@matchmail.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Shantanu Goel <sgoel01@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc1-ac2 NFS close-to-open question
Date: Mon, 5 May 2003 19:28:13 -0700 [thread overview]
Message-ID: <20030506022813.GB8350@matchmail.com> (raw)
In-Reply-To: <shshe8k6ijs.fsf@charged.uio.no>
On Sun, Apr 27, 2003 at 05:56:07PM +0200, Trond Myklebust wrote:
> >>>>> " " == Shantanu Goel <sgoel01@yahoo.com> writes:
>
> > if (!(NFS_SERVER(inode)->flags & NFS_MOUNT_NOCTO)) {
> > err =
> > _nfs_revalidate_inode(NFS_SERVER(inode),inode);
> > if (err)
> > goto out;
> > }
>
> > If we desire close-to-open consistency, and assuming my reading
> > of the code is correct, is this a typo?
>
> Duh... Now *that* is downright embarassing...
> Yup. Damn right...
>
> Cheers,
> Trond
Might that cause this too:
May 5 15:32:10 fileserver kernel: lockd: can't encode arguments: 5
May 5 15:33:08 fileserver last message repeated 18 times
May 5 15:34:07 fileserver last message repeated 27 times
May 5 15:35:07 fileserver last message repeated 23 times
May 5 15:36:08 fileserver last message repeated 10 times
May 5 15:37:09 fileserver last message repeated 22 times
May 5 15:37:34 fileserver last message repeated 9 times
May 5 17:24:47 fileserver kernel: lockd: can't encode arguments: 5
May 5 17:25:45 fileserver last message repeated 21 times
I have one system exporting a 112GB reiserfs partition and I've tested it
with two kernels:
2.4.20-rmap15e
2.4.21-rc1-rmap15g
2.4.21-rc1-rmap15g is giving the above error, and 2.4.20-rmap15e is not.
I'll leave it on 2.4.20-rmap15e for now and let you know if there are any
errors on that one too.
00:00.0 Host bridge: Intel Corp. 440FX - 82441FX PMC [Natoma] (rev 02)
00:07.0 ISA bridge: Intel Corp. 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
00:07.1 IDE interface: Intel Corp. 82371SB PIIX3 IDE [Natoma/Triton II]
00:07.2 USB Controller: Intel Corp. 82371SB PIIX3 USB [Natoma/Triton II] (rev 01)
00:08.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01)
00:0c.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24)
I can include .config files too if needed.
Thanks,
Mike
next prev parent reply other threads:[~2003-05-06 2:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 15:12 2.4.21-rc1-ac2 NFS close-to-open question Shantanu Goel
2003-04-27 15:56 ` Trond Myklebust
2003-05-06 2:28 ` Mike Fedyk [this message]
2003-05-06 12:50 ` Trond Myklebust
2003-05-06 16:21 ` Mike Fedyk
2003-05-07 19:37 ` Mike Fedyk
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=20030506022813.GB8350@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sgoel01@yahoo.com \
--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;
as well as URLs for NNTP newsgroup(s).