From: Andries Brouwer <aebr@win.tue.nl>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NFS regression in 2.6
Date: Tue, 19 Aug 2003 21:06:23 +0200 [thread overview]
Message-ID: <20030819210623.A2195@pclin040.win.tue.nl> (raw)
In-Reply-To: <3F4268C1.9040608@redhat.com>; from drepper@redhat.com on Tue, Aug 19, 2003 at 11:13:21AM -0700
On Tue, Aug 19, 2003 at 11:13:21AM -0700, Ulrich Drepper wrote:
> This is a problem which pops up in the glibc test suite. It's been like
> this for many weeks, even months. I just hadn't time to investigate.
> But the problem is actually very easy.
>
> Go into a directory mounted via NFS. You need write access. Then
> execute this little program:
>
> The result is always, 100% of the time, a failure in ftruncate. The
> kernel reports ESTALE. This has not been a problem in 2.4 and not even
> in 2.6 until <mumble> months ago. And of course it works with local disks.
I just tried NFS client 2.6.0-test3, NFS server 2.0.34, try test on client.
No problems. ftruncate did not fail.
(Do you require some NFS version?)
next prev parent reply other threads:[~2003-08-19 19:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 18:13 Ulrich Drepper
2003-08-19 18:49 ` Ulrich Drepper
2003-08-19 19:19 ` Tupshin Harper
2003-08-19 19:06 ` Andries Brouwer [this message]
2003-08-19 19:15 ` Ulrich Drepper
2003-08-20 2:26 ` Andries Brouwer
2003-08-20 5:37 ` Trond Myklebust
2003-08-20 17:24 ` Andries Brouwer
2003-08-20 18:43 ` Trond Myklebust
2003-08-20 19:02 ` Ulrich Drepper
2003-08-20 19:52 ` Andries Brouwer
2003-08-20 20:02 ` Trond Myklebust
2003-08-21 0:28 ` NFS regression in 2.6 -- gnome problem Tupshin Harper
2003-08-21 0:38 ` Andries Brouwer
2003-08-21 1:07 ` Tupshin Harper
2003-08-21 3:05 ` NFS regression in 2.6 Ulrich Drepper
2003-08-20 17:43 ` Ulrich Drepper
2003-08-20 18:06 ` Andries Brouwer
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=20030819210623.A2195@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=drepper@redhat.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
all inboxes | Powered by JetHome®