avati at zresearch.com
Mon Apr 30 15:47:40 UTC 2007
the fix is in the source repository. you can use the latest TLA
checkout. we generally maintain the TLA source repostiroy pretty
stable. but if you production site runs any mission critical jobs it
would be wise to use a relase tarball. Just curious, for what
applications are you using glusterfs for?
On Mon, Apr 30, 2007 at 09:57:57AM -0400, Amrik Singh wrote:
> Hi Anand,
> Thanks for the quick response. We are planning to use Gluster in
> production environment and would be using only the stable release. I
> guess we would have to wait a while for this fix to be reflected in a
> production release. We might ignore this problem and go ahead with our
> deployment with the current release. Do you think that might cause any
> problems ?
> Anand Avati wrote:
> > this was a bug in the way the return value of listxattr() method was
> >handled in glusterfs fuse client code. I have he fix in my devel tree
> >but the savannah tla servers seem to be down temporarily. will commit
> >it as soon as they come back up.
> >On Sun, Apr 29, 2007 at 04:24:21PM -0400, Amrik Singh wrote:
> >>While testing the glusterfs we are having a problem reading the extended
> >>attributes from a glusterfs mount.
> >>linux:/mnt/storage # getfattr hello.txt
> >>getfattr: hello.txt: Input/output error
> >>The client is mounting a glusterfs volume from two bricks (brick01 and
> >>On the client I mount the volume using the following command:
> >>glusterfs -s brick01 /mnt/storage
> >>Can someone please guide us in the right direction to fix this problem.
> >>Gluster-devel mailing list
> >>Gluster-devel at nongnu.org
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
sleep (years2secs (7500000));
More information about the Gluster-devel