From: Anton Starikov <ant.starikov@gmail.com>
To: Anton Starikov <ant.starikov@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS4 in combination with root over NFS3, hangs and dedlocks
Date: Tue, 30 Mar 2010 20:30:46 +0200 [thread overview]
Message-ID: <EDDF2B79-DBFA-4701-BEFF-0AEACD63A3DC@gmail.com> (raw)
In-Reply-To: <EE102A23-736F-4905-BAAF-1BF03064F529@gmail.com>
If it is already resolved problem, can someone point me into direction of particular patch?
Anton.
On Mar 29, 2010, at 5:14 PM, Anton Starikov wrote:
> Hi,
>
> Early (year ago and recently) I reported about my faults in getting working NFS4 mounts (primary automounting /home) with system booted with NFSv3-root. It always used to silently hang nodes with zero output in the logs. It was definitely client issue (I tried it with different versions of linux and solaris servers)
>
> Although I can't get simple and reproducible test-case, because hangs appears randomly, it can happen in 1hour, it can happen in 5 days, but it always will happen after some time. But this time I got some some improvement.
>
> With 2.6.32.9-70.fc12.x86_64 kernel and fresh nfs-utils from Fedora-12, after NFS4 mounts hangs, NFS3 mounts and node itself still continue to work, which gives chance to investigate problem.
>
> Can you give me instruction how to collect all necessary information to figure out where the bug is?
>
> As starting point I will attach output of echo "t" > sysrq-trigge, list of NFS mounts.
>
> Thanks,
> Anton.
>
> # cat /proc/mounts | grep nfs
> 172.19.8.1:/export/share/cluster/fedora-root / nfs ro,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=udp,port=65535,timeo=7,retrans=3,sec=sys,mountport=65535,addr=172.19.8.1 0 0
> none /var/lib/nfs tmpfs rw,relatime 0 0
> sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
> 172.19.8.1:/export/share/cluster/admin /root nfs rw,noatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,noacl,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.19.8.1,mountvers=3,mountport=44114,mountproto=tcp,addr=172.19.8.1 0 0
> 172.19.8.1:/export/share/cluster/checkpoint /mnt/checkpoint nfs rw,noatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,noacl,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.19.8.1,mountvers=3,mountport=52574,mountproto=udp,addr=172.19.8.1 0 0
> 172.19.8.1:/export/share/software /software nfs rw,noatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,noacl,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.19.8.1,mountvers=3,mountport=44114,mountproto=tcp,addr=172.19.8.1 0 0
> 172.19.8.1:/export/share/cluster/torque /var/torque nfs rw,noatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,noacl,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.19.8.1,mountvers=3,mountport=44114,mountproto=tcp,addr=172.19.8.1 0 0
> 172.19.8.1:/export/share/common/ /common nfs4 rw,noatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=172.19.8.133,addr=172.19.8.1 0 0
> 172.19.8.1:/export/home/alfons/ /home/alfons nfs4 rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=172.19.8.133,addr=172.19.8.1 0 0
>
> <log1.txt.gz>
>
next prev parent reply other threads:[~2010-03-30 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 15:14 NFS4 in combination with root over NFS3, hangs and dedlocks Anton Starikov
2010-03-30 18:30 ` Anton Starikov [this message]
2010-03-30 19:00 ` Chuck Lever
2010-03-30 19:11 ` NFS4 in combination with root over NFS3, hangs and deadlocks Anton Starikov
2010-03-30 19:27 ` Chuck Lever
2010-03-30 20:59 ` Anton Starikov
2010-03-31 0:09 ` Anton Starikov
2010-03-31 0:35 ` Anton Starikov
2010-04-02 12:48 ` NFS4 random hangs Anton Starikov
2010-04-02 17:22 ` Chuck Lever
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=EDDF2B79-DBFA-4701-BEFF-0AEACD63A3DC@gmail.com \
--to=ant.starikov@gmail.com \
--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