Bug 784745 - Solaris NFS client hangs with GlusterFS
Summary: Solaris NFS client hangs with GlusterFS
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterfs
Version: 1.0
Hardware: x86_64
OS: Solaris
medium
high
Target Milestone: ---
: ---
Assignee: Vinayaga Raman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-26 01:28 UTC by Dan Moraru
Modified: 2014-03-31 01:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-17 11:53:41 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Dan Moraru 2012-01-26 01:28:34 UTC
Description of problem:

Solaris 10 NFS client hangs while communicating with built-in GlusterFS NFS server.  Filesystem is distributed across 252 peers running RHEL6 and is configured as follows:

nfs.register-with-portmap: off
nfs.port: 38467
nfs.volume-access: read-only
nfs.ports-insecure: on

Each peer NFS-mounts the filesystem locally without problems.  Mounting from Solaris using e.g. 'mount -o proto=tcp,vers=3 nfs://node251:38467/cache /gfs/frames' works as well, but hangs when attempting to access subdirectories 2 levels deep.


Version-Release number of selected component (if applicable):

3.2.5


How reproducible:

always

Steps to Reproduce:
1.
2.
3.
  
Actual results:

# uname -a
SunOS qfs-nfs1 5.10 Generic_147441-07 i86pc i386 i86pc
# mount -o proto=tcp,vers=3 nfs://node251:38467/cache /gfs/frames
# df -h /gfs/frames
Filesystem             size   used  avail capacity  Mounted on
nfs://node251:38467/cache
                        93T    52T    41T    56%    /gfs/frames
# cd /gfs/frames
# ls
A6     S6     VSR2   VSR3   trend
# ls S6
L1           L3           LDAShoft     LDAShoftC02
# ls S6/L1
NFS server node251 not responding still trying



Expected results:


Additional info:

Comment 2 Krishna Srinivas 2012-08-14 12:20:21 UTC
Dan, Please try release 3.3 as 3.2.5 is old.

Comment 3 Krishna Srinivas 2012-08-17 11:53:41 UTC
Closing the bug as 3.3 has gone undergone good testing from solaris clients. Please re-open if the bug is seen.


Note You need to log in before you can comment on or make changes to this bug.