After my initial success in removing the "Unify" block from my config, i rebooted each machine in the test network (to get a nice fresh start), and now i was unable to access the mountpoint properly. Note the following cut and paste from the user session on the client : [root@test-dma-38 gfs-mount]# ls -l total 0 [root@test-dma-38 gfs-mount]# ls -l ls: cannot access data: No such file or directory ls: cannot access meta: No such file or directory ls: cannot access textfile.txt: No such file or directory total 0 d????????? ? ? ? ? ? data d????????? ? ? ? ? ? meta -????????? ? ? ? ? ? textfile.txt [root@test-dma-38 gfs-mount]# ls -l total 0 [root@test-dma-38 gfs-mount]# ls -l total 0 [root@test-dma-38 gfs-mount]# ls -l total 0 [root@test-dma-38 gfs-mount]# ls -l ls: cannot access data: No such file or directory ls: cannot access meta: No such file or directory ls: cannot access textfile.txt: No such file or directory total 0 d????????? ? ? ? ? ? data d????????? ? ? ? ? ? meta -????????? ? ? ? ? ? textfile.txt [root@test-dma-38 gfs-mount]# ls -l total 0 [root@test-dma-38 gfs-mount]# This condition remained for about 15 minutes. On a whim, i entered the "data" directory, and did an "ls" there - the contents of the directory displayed as normal. When i went back one level to the base mountpoint, i did another "ls" : [root@test-dma-38 gfs-mount]# ls -l total 24 drwx------ 102 root root 4096 2008-04-09 15:13 data drwx------ 2 root root 4096 2008-04-09 15:08 meta -rw-r--r-- 1 root root 80 2008-04-09 13:58 textfile.txt [root@test-dma-38 gfs-mount]# cat textfile.txt This is a text file ! [root@test-dma-38 gfs-mount]# It would appear that entering the "data" sub-directory sort of "reset" the mountpoint or something. Very odd. Any ideas ? -- Daniel Maher <dma AT witbe.net>
