Hello,
I am trying to configure a volume using DHT, however after I mount it,
the mount point looks rather strange and when I try to do 'ls' on it I
get:
ls: /mnt/gtest: Stale NFS file handle
I can create files and dirs in the mount point, I can list them but I
cant list the mount point itself.
Example:
the folume is mounted on /mnt/gtest
[root at storage2]# ls -l /mnt/
?--------- ? ? ? ? ? gtest
If I try to list the mountpoint:
[root at storage2 ~]# ls -l /mnt/gtest
ls: /mnt/gtest: Stale NFS file handle
Can anyone please help me fix this.
Here is the systeminfo:
OS: CentOS 5 x86_64
Kernel: 2.6.18-194.3.1.el5
Fuse: 2.7.4glfs11
glusterfs 3.0.4 built on May 17 2010 08:28:27
Repository revision: v3.0.4
The volume files:
#####################################
### GlusterFS Server Volume File ##
#####################################
volume storage1-test1
type storage/posix
option directory /mnt/test1
end-volume
volume storage1-test2
type storage/posix
option directory /mnt/test2
end-volume
volume locksstorage1-test1
type features/locks
option mandatory-locks on
subvolumes storage1-test1
end-volume
volume locksstorage1-test2
type features/locks
option mandatory-locks on
subvolumes storage1-test2
end-volume
volume ioth-locksstorage1-test1
type performance/io-threads
option thread-count 8
subvolumes locksstorage1-test1
end-volume
volume ioth-locksstorage1-test2
type performance/io-threads
option thread-count 8
subvolumes locksstorage1-test2
end-volume
volume server
type protocol/server
option transport-type tcp
option auth.login.ioth-locksstorage1-test1.allow storuser
option auth.login.storuser.password xxxxxxxxxxxxxxxxxxxxxxxxx
option auth.login.ioth-locksstorage1-test2.allow storuser
option auth.login.storuser.password xxxxxxxxxxxxxxxxxxxxxxxxx
subvolumes ioth-locksstorage1-test1 ioth-locksstorage1-test2
end-volume
#####################################
### GlusterFS Client Volume File ##
#####################################
volume client-storage1-test1
type protocol/client
option transport-type tcp
option remote-host 10.15.19.215
option frame-timeout 1000
option ping-timeout 30
option username storuser
option password xxxxxxxxxxxxxxxxxxxxxxxxxxx
option remote-subvolume ioth-locksstorage1-test1
end-volume
volume client-storage1-test2
type protocol/client
option transport-type tcp
option remote-host 10.15.19.215
option frame-timeout 1000
option ping-timeout 30
option username storuser
option password xxxxxxxxxxxxxxxxxxxxxxxxxxxx
option remote-subvolume ioth-locksstorage1-test1
end-volume
volume distribute
type cluster/distribute
subvolumes client-storage1-test1 client-storage1-test2
# option lookup-unhashed on
end-volume
Thank you
Regards,
Deyan
On 31.05.2010 11:39, Deyan Chepishev wrote:> Hello, > > I am trying to configure a volume using DHT, however after I mount it, > the mount point looks rather strange and when I try to do 'ls' on it I > get: > > ls: /mnt/gtest: Stale NFS file handle > > I can create files and dirs in the mount point, I can list them but I > cant list the mount point itself. > > Example: > > the folume is mounted on /mnt/gtest > > [root at storage2]# ls -l /mnt/ > > ?--------- ? ? ? ? ? gtest > > If I try to list the mountpoint: > [root at storage2 ~]# ls -l /mnt/gtest > ls: /mnt/gtest: Stale NFS file handle > > Can anyone please help me fix this. > > Here is the systeminfo: > > OS: CentOS 5 x86_64 > Kernel: 2.6.18-194.3.1.el5 > Fuse: 2.7.4glfs11 > glusterfs 3.0.4 built on May 17 2010 08:28:27 > Repository revision: v3.0.4 > > The volume files: >Did you try to umount and mount it again? From my tests with gluster when I start server and first time mount the share it behaves like you said, but if re-mount it, it works. This is not a solution, just what I found.
We need the logs to figure out the exact problem. Please run the glusterfs command while mounting through FUSE with the following command line option: glusterfs -f <your-dht-volfile> -L TRACE -l /tmp/dhtlog /mnt/gtest Then perform the same operations and email us the dhtlog file, and we'll see whats going on. Thanks -Shehjar Deyan Chepishev wrote: