[Gluster-users] STALE NFS Handle (Transport endpoint is not connected)

Heiko Schröter schroete at iup.physik.uni-bremen.de
Wed Mar 16 12:26:10 UTC 2011


the following produces STALE NFS Handle (Transport endpoint is not connected)
Scenario: 2 bricks, 1 client
Version: 3.1.2

1) Bring gluster system up
rd32 ~ # gluster volume info
Volume Name: test-volume
Type: Distribute
Status: Started
Number of Bricks: 2
Transport-type: tcp
Brick1: rd32:/mnt/gluster1
Brick2: rd33:/mnt/gluster1

1a) mount /mnt/gluster on client.

2) Bring bricks down

3) Try to access /mnt/gluster on client:
client# ls -la /mnt/gluster
ls: cannot access /mnt/gluster: Transport endpoint is not connected

3) Start glusterd on Brick1:
client# ls -la /mnt/gluster
ls: cannot access /mnt/gluster: Stale NFS file handle

4) Start glusterd on Brick2:
client# ls -la /mnt/gluster
total 102408
drwxr-xr-x 2 root root        58 Mar 14 15:48 .
drwxr-xr-x 7 root root      4096 Mar  2 10:21 ..
-rw-r--r-- 1 root root         1 Mar 14 14:36 .version
-rw-r--r-- 1 root root 104857600 Mar 14 15:48 willi.dat

STALE NFS Handle only vanishs when ALL bricks are up and running, when started as above.
This is reproducable.

Expected behaviour:
Client should never ever see a STALE NFS Handle.
If no brick is running -> /mnt/gluster should be just empty.
If at least one brick is running -> /mnt/gluster should show the files on that single brick.

Thanks and Regards

More information about the Gluster-users mailing list