From: "Malte Schröder" <MalteSch@gmx.de>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with nfs4, kernel 2.6.13.2
Date: Sun, 09 Oct 2005 22:57:22 +0200 [thread overview]
Message-ID: <43498432.8060503@gmx.de> (raw)
In-Reply-To: <200509262218.15885.MalteSch@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]
Malte Schröder wrote:
> On Monday 26 September 2005 14:28, Trond Myklebust wrote:
>
>>Also, is this something that is NFSv4 only, or can you reproduce it on
>>NFSv2/v3 too?
>
>
> I have been running my "stress test" for a few hours with nfsv3, without
> problems.
> I tried over nfsv4 again and it crashed after a few minutes.
>
I had time to try this with 2.6.12.5, I was not able to reproduce the
error there.
I also found the following post on LKML:
Bret Towe wrote:
> On 9/8/05, Bret Towe <magnade@gmail.com> wrote:
>
>>On 9/6/05, J. Bruce Fields <bfields@fieldses.org> wrote:
>>
>>>On Mon, Sep 05, 2005 at 08:40:53PM -0700, Bret Towe wrote:
>>>
>>>>Pid: 14169, comm: xmms Tainted: G M 2.6.13
>>>
>>>Hm, can someone explain what that means? A proprietary module was
>>>loaded then unloaded, maybe?
>>>
>>>You may also want to retest with
>>>
>>>http://www.citi.umich.edu/projects/nfsv4/linux/kernel-patches/2.6.13-1/linux-2.6.13-001-NFS_ALL_MODIFIED.dif
>>>
>>>applied, to make sure there isn't a patch in Trond's series that already
>>>fixes the bug.
>>>
>>>--b.
>>>
>>
>>ive been running this since i got the url and so far i havent hit it
>>ive also been a bit busy so i havent been able to make sure its good
>>this weekend i should be able to test it and make sure its solved
>>
>
> ran it pretty hard over the weekend and i had no crashs at all
> so i think its safe to say this patch fixes the issues i was seeing
The above server is currently unreachable from my part of the net but
Bret Towe seemed to have the same problem as I have. Since the problem
also appears when using 2.6.14-rc3 I think the patch should be looked at
and maybe considered for inclusion. As soon as I gain access to that
patch I will test it and report my results.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-10-09 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 13:16 Problem with nfs4, kernel 2.6.13.2 Malte Schröder
2005-09-26 12:28 ` Trond Myklebust
2005-09-26 14:21 ` Malte Schröder
2005-09-26 20:18 ` Malte Schröder
2005-10-09 20:57 ` Malte Schröder [this message]
2005-10-10 15:25 ` Trond Myklebust
2005-10-10 19:33 ` Malte Schröder
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=43498432.8060503@gmx.de \
--to=maltesch@gmx.de \
--cc=Trond.Myklebust@netapp.com \
--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