| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
RE: [Xen-users] NFS goes down, XEN hangs
Actually "strace w" did the trick and showed me "w" is hanging when trying to
read from "/usr/sbin/tapdisk2" referencing "Server1".
It seems that NFS comes back online by itself (I can "ls" inside dom0, as I
said), but not tapdisk2.
Probably tapdisk2 is the one to be blamed.
Probably this belongs to xen-devel...
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Fajar A. Nugraha
Sent: Sunday, August 21, 2011 11:45 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] NFS goes down, XEN hangs
On Mon, Aug 22, 2011 at 9:27 AM, Antonio Pina (antonio.pina)
<antonio.pina@xxxxxxxxxxx> wrote:
> Thank you for your answer.
>
> I understand and agree with your point but it's not the case. As soon
> as Server1 comes back, the NFS directory becomes available again (ls
> -l /server1 works). The CPU is low as usual and I can use some
> commands like "xl list",
the default nfs behaviour does that
> but now other commands, like "w" I said before.
You might be able to get better help from other people with more nfs expertise.
My best guess is that "w" is somehow trying to interact with the process
accessing the stale nfs mount (at least "strace w"
shows it's accessing /proc/[pid]/stat), and since the process is
uninterruptible "w" has to wait (thus the appearance of "hang").
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home