From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: ruediger@theo-phys.uni-essen.de
Cc: linux-kernel@vger.kernel.org, 325117@bugs.debian.org
Subject: Re: NFS client problem with kernel 2.6 and SGI IRIX 6.5
Date: Wed, 19 Oct 2005 14:13:41 -0700 [thread overview]
Message-ID: <1129756421.8971.19.camel@lade.trondhjem.org> (raw)
In-Reply-To: <200510191652.SAA13594@next12.theo-phys.uni-essen.de>
on den 19.10.2005 klokka 18:52 (+0200) skreiv Ruediger Oberhage:
> Hello again.
>
> Some first findings regarding nfs problems:
>
> At first I have to apologize for my memory (again :-)) serving me
> wrong: I did state, that the "find /nfsDir -print" problem was
> (generally) gone with the 2.6.12 kernel; this is wrong(!).
>
> The problem does exist for both (Debianized) kernels 2.6.8 as well
> as 2.6.12 (the details follow below in the 'strace'-dump). The
> (find-)problem does NOT exist for the (2.6.12-)kernel delivered on
> the KNOPPIX 4.0 DVD!!! So there is a cure for some kernel for this
> one. The 'resources'-problem (OpenOffice/Mathematica) still remains
> for this kernel, too!
Recent kernels (2.6.13 and above - sorry, I though it was 2.6.12) have
the following patch applied
http://client.linux-nfs.org/Linux-2.6.x/2.6.12/linux-2.6.12-43-dirent_fix.dif
This should normally suffice to fix the SGI problem.
Cheers,
Trond
next prev parent reply other threads:[~2005-10-19 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 9:05 NFS client problem with kernel 2.6 and SGI IRIX 6.5 Ruediger Oberhage
2005-10-14 18:22 ` Trond Myklebust
2005-10-19 16:52 ` Ruediger Oberhage
2005-10-19 21:13 ` Trond Myklebust [this message]
2005-10-26 3:42 ` Bug#325117: " Horms
2005-10-26 8:04 ` Ruediger Oberhage
2005-10-28 14:35 ` Ruediger Oberhage
-- strict thread matches above, loose matches on Subject: below --
2005-10-17 14:17 James Pearson
2005-10-17 15:40 ` Ruediger Oberhage
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=1129756421.8971.19.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=325117@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ruediger@theo-phys.uni-essen.de \
/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