aurfalien at gmail.com
2011-Apr-18 19:01 UTC
[CentOS] rhel nfs bug with 5.5 - nfsd: blocked for more then 120 sec
Hi all, I ran into this bug on my NFS server which is serving an XFS fs; https://bugzilla.redhat.com/show_bug.cgi?id=616833 It was suggested using bind mounts. My current fstab on my server is; /dev/sdc1 /SHARE xfs defaults,noatime,nodiratime,logbufs=8,uquota 1 2 Unsure how to integrate bind mounts in this scheme to see if I can avoid this bug until it is fixed. Any ideas? - aurf
Les Mikesell
2011-Apr-18 19:46 UTC
[CentOS] rhel nfs bug with 5.5 - nfsd: blocked for more then 120 sec
On 4/18/2011 2:01 PM, aurfalien at gmail.com wrote:> Hi all, > > I ran into this bug on my NFS server which is serving an XFS fs; > > https://bugzilla.redhat.com/show_bug.cgi?id=616833 > > It was suggested using bind mounts. > > My current fstab on my server is; > > /dev/sdc1 /SHARE xfs defaults,noatime,nodiratime,logbufs=8,uquota 1 2 > > Unsure how to integrate bind mounts in this scheme to see if I can > avoid this bug until it is fixed. > > Any ideas?That's not the mount that matters. The suggestion had to do with loopback mounts where the same machine is a client. Those could be bind mounts, symlinks, or just pointed directly at the real location instead. If you aren't doing that you might just need more memory. -- Les Mikesell lesmikesell at gmail.com
Possibly Parallel Threads
- mail location filesystem noatime, nodiratime?
- Re-mount a drive using its label name
- LVM + XFS + external log + snapshots
- 'error=No space left on device' but, there is plenty of space all nodes
- 'error=No space left on device' but, there is plenty of space all nodes