Hi,
I have a very simple two server setup with Unify. The servers are running
FreeBSD ( 1.3.8 ) and the client is SuSE 10.3 ( 1.3.8 )
The servers ( FreeBSD ) are running ZFS and UFS, the name space exists on
the client which is XFS.
In most cases, things are running sweet.
But, I have been getting this which is causing my app. to bomb out ( eg ):
2008-05-12 01:50:49 E [unify.c:325:unify_lookup] bricks: returning
ESTALE for /jre/lib/locale/sv(46912587703840) [translator generation (6)
inode generation (3)]
2008-05-12 01:50:49 E [fuse-bridge.c:459:fuse_entry_cbk] glusterfs-fuse:
46164509: (34) /jre/lib/locale/sv => -1 (116)
If I actually 'CWD' to that directory from the client and 'ls -al', I can
see the files there but get something like ( eg ):
2008-05-12 06:08:04 E [fuse-bridge.c:2176:fuse_xattr_cbk]
glusterfs-fuse: 159472: (20) /java/lib/fontconfig.bfc => -1 (45)
The actual ls command returns something like : Level 2 not Syncronized
1. On the namespace server there is a reference to the file there
2. On Server 1 the file actually exists
3. On Server 2 the file isn't there
It could be the case that these files existed in the backend ( server side
) before the unify was done, I believe in the past if I come across files
like this, if I delete them from the client and let them be re-created it
seems ok.
Is there anything I can do , or am I better off just blowing away these
directories and allow the creation of the files again?
cheers
--
Paul Arch
