From: Jeff Garzik <jeff@garzik.org>
To: Trond.Myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: major NFSv4 client regression (-rc7)
Date: Thu, 10 Jan 2008 15:41:19 -0500 [thread overview]
Message-ID: <20080110204119.GA714@havoc.gtf.org> (raw)
Server: Linux 2.6.24-rc6 (x86-64/Fedora 8)
Good client: Linux 2.6.24-rc6-ge697789d (x86-64/Fedora 7)
Bad client: Linux 2.6.24-rc7-gfd0b45df (x86-64/Fedora 7)
Situation: home dir via NFS
My home setup is a standard homedir-over-NFS setup, using NFSv4 on both
client and server. I just rebooted into the latest upstream kernel, and
I am getting NFS client hangs all over the place:
[jgarzik@core firefox]$ cat profiles.ini
hangs here, for 15 minutes so far and counting...
('core' is the client machine)
and I first noticed this when firefox and thunderbird were hanging, when
I tried to start them after rebooting into the latest kernel. stracing
firefox yielding a hang in open:
("/g" is the NFS-mounted volume)
access("/usr/lib64/firefox-2.0.0.10/updates", F_OK) = -1 ENOENT (No such file or directory)
access("/g/g/.mozilla/firefox", F_OK) = 0
access("/g/g/.mozilla/firefox", F_OK) = 0
stat("/g/g/.mozilla/firefox/profiles.ini", {st_mode=S_IFREG|0664, st_size=94, ...}) = 0
open("/g/g/.mozilla/firefox/profiles.ini", O_RDONLY
hangs here, for 20 minutes so far and counting...
As you can see from the trace, and as I can report simply by being able
to send this message, SOME file accesses over NFS work just fine.
Accessing the file works when logged into the server, so its not disk
corruption or something like that.
Neither client nor server have anything interesting in dmesg -- in fact
nothing in dmesg beyond the normal boot messages have been printed.
Let me know what info I can provide... This is a 100% reproducible
regression, and this latest NFS client revision has made my local
NFS-over-homedir setup completely unusable. I am forced to return to
the known working client (Linux 2.6.24-rc6-ge697789d) just to run basic
apps.
Jeff
next reply other threads:[~2008-01-10 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 20:41 Jeff Garzik [this message]
2008-01-10 20:49 ` major NFSv4 client regression (-rc7) Andrew Morton
2008-01-10 20:50 ` Jeff Garzik
2008-01-10 20:51 ` Trond Myklebust
2008-01-10 21:04 ` Jeff Garzik
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=20080110204119.GA714@havoc.gtf.org \
--to=jeff@garzik.org \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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