Vijay Bellur <vbellur@xxxxxxxxxx> wrote: > If the problem happens with the basic posix translator and the implicit > fuse translator, we would have narrowed down the problem. If not, we can > start adding more translators into the custom volume file and arrive at > the set of translators that will cause this problem. Once it failed on creating a directory on fs root, but somehow it succeeded later. Here is the logon failure: [2012-10-18 17:13:30.754409] E [posix.c:125:posix_lookup] 0-foo-posix: null gfid for path /test [2012-10-18 17:13:30.754652] E [posix.c:142:posix_lookup] 0-foo-posix: lstat on (null) failed: Undefined error: 0 [2012-10-18 17:13:30.754820] W [fuse-resolve.c:81:fuse_resolve_entry_cbk] 0-fuse: 00000000-0000-0000-0000-000000000000/test: failed to resolve (Undefined error: 0) [2012-10-18 17:13:30.755111] W [fuse-bridge.c:464:fuse_lookup_resume] 0-glusterfs-fuse: 2: LOOKUP() (null) => -1 (Undefined error: 0) Once I managed to make the directory on root, creating a subdirectory fails with protocol error without anything in the log. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@xxxxxxxxxx
