xfs
[Top] [All Lists]

Re: Processes stuck in D state..

To: Gordon Henderson <gordon@xxxxxxxxxx>
Subject: Re: Processes stuck in D state..
From: Keith Owens <kaos@xxxxxxx>
Date: Thu, 07 Aug 2003 10:45:47 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: Your message of "Thu, 07 Aug 2003 00:13:06 +0100." <Pine.LNX.4.56.0308070003410.968@unicorn.drogon.net>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Thu, 7 Aug 2003 00:13:06 +0100 (BST), 
Gordon Henderson <gordon@xxxxxxxxxx> wrote:
>Maybe my original email was unclear, but this is an NFS server, not a
>client. Why would an NFS exported filesystem hang xfsdump? (or even du -k
>?)
>ie.
>
> 1149 ?        D      2:21 xfsdump -F -J -l 1 - /dev/md4
>
>This xfsdump is trying to dump /dev/md4 which is obviously local to the
>server and it's stuck. Why is it stuck?

From your original mail:

>>  9275 ?        D      2:02 du -k
>> 10103 ?        D      2:26 /usr/bin/find / ( -fstype NFS -o -fstype nfs -o
>> 21671 ?        D      1:28 /usr/bin/rsync -a --delete -H -x .  >> 
>> /mounts/local0.yesterday/
>> 13976 ?        D      1:16 du -k
>> 14776 ?        D      1:59 /usr/bin/find / ( -fstype NFS -o -fstype nfs -o

All operations that require filesystem locks.  They are queued up
behind some task that has grabbed a filesystem lock and is hung, IOW
these tasks are innocent victims of the real problem.  99.9%
probability that the real problem is a hung NFS event.

If you have kdb installed and active, drop into kdb and
  set LOGGING 1
  bta RD
  go
The trace will show what the hung tasks are waiting on.


<Prev in Thread] Current Thread [Next in Thread>