linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 7 May 2003 12:37:12 -0700	[thread overview]
Message-ID: <20030507193712.GI8350@matchmail.com> (raw)
In-Reply-To: <16055.44973.106804.436859@charged.uio.no>

On Tue, May 06, 2003 at 02:50:53PM +0200, Trond Myklebust wrote:
> >>>>> " " == Mike Fedyk <mfedyk@matchmail.com> writes:
> 
>      > Might that cause this too:
> 
>      > May 5 15:32:10 fileserver kernel: lockd: can't encode
>      > arguments: 5
> 
> No.
> 
>      > 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.
> 
> I'm confused. Are the rmap patches making changes to lockd?
> I certainly don't see the above errors in standard 2.4.21-rc1.

Oh, one more thing.

This is output from a server running 2.4.19-freeswan mounting an nfs export
from a reiserfs based 112GB export using 2.4.21-rc1-freeswan-rmap.  When the
112GBs are exported from 2.4.20-freeswan-rmap, there is no error.

I will retest, but I hope this isn't a bug making it through the pre & rc
process.

      parent reply	other threads:[~2003-05-07 19:25 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
2003-05-06 12:50     ` Trond Myklebust
2003-05-06 16:21       ` Mike Fedyk
2003-05-07 19:37       ` Mike Fedyk [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=20030507193712.GI8350@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).