Can you please attach the spec file? probably some stale binaries have got left over from the previous build.. what were the steps you did to uninstall glusterfs? does it work on a differnt system which had no traces of 1.2.3? thanks, avati 2007/6/25, Ian Grimstead <I.J.Grimstead@xxxxxxxxxxxxxxxx>:
I think something's up - I have just uninstalled 1.2.3 on each node, then obtained & built glusterfs--mainline--2.4; looks like you need to run autogen.sh to produce the "configure" script? Did that, installed... now I'm not getting any directories under my glusterfs mount, apart from a single (and empty) "/home". So I have: /media/glusterfs => gluster FS mount point ls -al /media/glusterfs gives: total 24 drwxr-xr-x 3 root root 4096 May 30 14:57 . drwxr-xr-x 3 root root 4096 May 11 17:32 .. drwxr-xr-x 4 root root 4096 Jun 11 13:46 home But, ls -al /media/glusterfs/home gives: total 0 Rather worrying. However, if I "cd" to a known directory, it works. This dir is also empty. If I "cat" a known file, it's there! Wierd. Log from client just shows "stat-prefetch:flush on: /" 3 times after initial handshake success of servers... I've turned off prefetch caching on the client - no difference. :o( Any idea what could have caused this? Ian
-- Anand V. Avati
