[Gluster-devel] ESTALE

[Amar S. Tumballi]

Hi,
 Yes, there are two factors here.

1. 'errno' incompatibility. (errno == 45 in BSD is EOPNOTSUPP, but on Linux
EL2NSYNC.)
2. xattr not supported.

the first one is already solved in mainline--3.0 branch, second one, I will
work on having solaris like port for BSD inside glusterfs. But may be after
few (1-3)weeks.

Regards,
Amar

On Mon, May 12, 2008 at 10:20 AM, Jordan Mendler <jmendler at ucla.edu> wrote:

> I am not sure if this is a factor or not, but I had trouble with
> FreeBSD/ZFS
> since their port does not yet support extended attributed. While I am not
> sure whether or not this matters for unify, I see a xattr message in your
> logs.
>
> Cordially,
> Jordan
>
> On Sun, May 11, 2008 at 7:54 PM, Paul Arch <paul at esidium.com.au> wrote:
>
> > 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
> >
> >
> >
> >
> >
> > _______________________________________________
> > Gluster-devel mailing list
> > Gluster-devel at nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/gluster-devel
> >
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>



-- 
Amar Tumballi
Gluster/GlusterFS Hacker
[bulde on #gluster/irc.gnu.org]
http://www.zresearch.com - Commoditizing Super Storage!