From: Martin Pool <mbp@sourcefrog.net>
To: r.ems@gmx.net
Cc: nfs@lists.sourceforge.net
Subject: Re: cat /proc/fs/nfs/exports hangs
Date: Thu, 4 Sep 2003 12:46:31 +1000 [thread overview]
Message-ID: <20030904124631.6ddb1fee.mbp@sourcefrog.net> (raw)
In-Reply-To: <3F54E248.30102@gmx.net>
On 2 Sep 2003 Richard Ems <r.ems@gmx.net> wrote:
> Hi all!
>
> This is a dual Athlon system with SuSE 8.2.
> Kernel is SuSE's k_smp-2.4.21-4.
>
> After 32 days of uptime nfs exports stopped working.
> While trying to restart the nfs server them I found that running
> "rcnfsserver restart" hangs on exportfs (process ind D state)
>
> Also a simple "cat /proc/fs/nfs/exports" hangs (process in D state).
>
> The last lines from "strace cat /proc/fs/nfs/exports" show:
>
> munmap(0x40016000, 59621) = 0
> open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) = 3
> fstat64(3, {st_mode=S_IFREG|0644, st_size=32058672, ...}) = 0
> mmap2(NULL, 2097152, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40158000
> close(3) = 0
> brk(0) = 0x804c68c
> brk(0x804d68c) = 0x804d68c
> brk(0) = 0x804d68c
> brk(0x804e000) = 0x804e000
> fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0
> open("/proc/fs/nfs/exports", O_RDONLY|O_LARGEFILE) = 3
> fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> read(3, <unfinished ...>
I don't know the answer, but you can get some more potentially
interesting information by looking at the wait channel of cat and of
other relevant processes.
# ps axo pid,cmd,wchan
--
Martin
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-09-04 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 18:32 cat /proc/fs/nfs/exports hangs Richard Ems
2003-09-04 2:46 ` Martin Pool [this message]
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=20030904124631.6ddb1fee.mbp@sourcefrog.net \
--to=mbp@sourcefrog.net \
--cc=nfs@lists.sourceforge.net \
--cc=r.ems@gmx.net \
/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