From: David Warren <warren-qmPYOCrcNLLyFCzt5hm0YvZ8FUJU4vz8@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: server locks up at boot
Date: Thu, 16 Jul 2009 13:44:00 -0700 [thread overview]
Message-ID: <4A5F9110.4050208@atmos.washington.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
We have been having a problem for a while now with kernels ranging from
2.6.26 through 30. When a boots and starts the nfs server, it reads the
/var/lib/nfs/v4recovery directory. If this directory is empty everything
is fine. If it is not, all nfs related processes go into D wait and
never return. Any other attempt to read the directory results in that
process getting stuck in D wait as well. This happens on a variety of
systems, all running Debian Lenny (happened with etch also) with kernels
ranging from 2.6.26 - 2.6.31-rc2 serving disks via nfs4. if you boot
single user and clear out the directory, everything is fine. Also, there
is never any problem logged anywhere.
So, my questions are:
What is this directory really used for? It doesn't seem to need it to
reestablish connections
Anyone have any idea what is going on or suggestions for finding out?
[-- Attachment #2: warren.vcf --]
[-- Type: text/x-vcard, Size: 342 bytes --]
begin:vcard
fn:David Warren
n:Warren;David
org:Atmospheric Sciences
adr:Dept of Atmospheric Sciences, Box 351640;;University of Washington;Seattle;WA;98195-1640;USA
email;internet:warren-qmPYOCrcNLLyFCzt5hm0YvZ8FUJU4vz8@public.gmane.org
title:Software Engineer
tel;work:206 543-0945
url:http://www.atmos.washington.edu
version:2.1
end:vcard
next reply other threads:[~2009-07-16 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 20:44 David Warren [this message]
[not found] ` <4A5F9110.4050208-qmPYOCrcNLLyFCzt5hm0YvZ8FUJU4vz8@public.gmane.org>
2009-07-22 16:32 ` server locks up at boot J. Bruce Fields
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=4A5F9110.4050208@atmos.washington.edu \
--to=warren-qmpyocrcnllyfczt5hm0yvz8fuju4vz8@public.gmane.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