Please check http://review.gluster.org/#change,4114
Avati
On Fri, Oct 19, 2012 at 9:24 PM, Emmanuel Dreyfus <m...@netbsd.org> wrote:
> Vijay Bellur <vbel...@redhat.com> wrote:
>
> > Not really. You could start with a custom volume file like:
> >
> > volume foo-posix
> > type storage/posix
> > option directory /tmp/foo1
> > option volume-id 3103a755-72fb-4d0d-8cd4-89845592ad98
> > end-volume
>
> I changed volume-id to glusterd-uuid to shut up a warning.
>
> After a few tests, I am now conviced the protocol error is a consequence
> of an earlier bug. On a fresh volume that contains nothing, ls -l on an
> unexisting file at volume root causes a crash in lookup code.
>
> [posix.c:129:posix_lookup] 0-foo-posix: null gfid for path /x
> [posix.c:154:posix_lookup] 0-foo-posix: lstat on (null) failed:
> Undefined error: 0
>
> This is where it comes from:
>
> #define MAKE_INODE_HANDLE(rpath, this, loc, iatt_p) do { \
> if (uuid_is_null (loc->gfid)) { \
> gf_log (this->name, GF_LOG_ERROR, \
> "null gfid for path %s", loc->path); \
> break; \
> } \
>
> Is it something sane?
>
> --
> Emmanuel Dreyfus
> http://hcpnet.free.fr/pubz
> m...@netbsd.org
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/gluster-devel
>
_______________________________________________
Gluster-devel mailing list
Gluster-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/gluster-devel
