[Gluster-devel] Reporting on OS X bricks

[Dennis Schafroth]

Using ZFS works with linkat and symlinks. 

I did see some cases of: 

[2015-03-01 15:15:05.554027] E [posix.c:188:posix_lookup] 0-ztank-posix: post-operation lstat on parent /Users/dennis/tank/brick1/.glusterfs/b4/f5/b4f54487-9aa4-451d-ab55-85d0414ea7ab failed: No such file or directory

when I was deleting files as well as 

[2015-03-01 15:27:59.194055] E [server-rpc-fops.c:768:server_getxattr_cbk] 0-ztank-server: 230123: GETXATTR / (00000000-0000-0000-0000-000000000001) (user.com.apple.FinderInfo) ==> (Attribute not found)

which I think is harmless, but looks weird with the zero UUID.

cheers, 
:-Dennis

> On 28 Feb 2015, at 12:40 , Dennis Schafroth <dennis at schafroth.dk> wrote:
> 
> Hi
> 
> I am testing glusterfs on OS X (yosemite) as bricks  and this does not go well with symbolic links due to what I believe is missing support for hardlinking to a symlink (not its target) in HFS+. 
> 
> So when doing a symlink to a file like:
> 
> $ touch from_file
> $ ln -s from_file to_symlink
> 
> I am getting:
> 
> [2015-02-25 07:08:03.092538] W [posix-handle.c:711:posix_handle_hard] 0-repl-posix: link /export/data/brick1/symlink -> /export/data/brick1/.glusterfs/0f/eb/0feb5989-30c9-4f09-812a-dfbfc9e9956a failed (Operation not supported)
> [2015-02-26 22:16:26.074432] E [posix.c:1796:posix_symlink] 0-repl-posix: setting gfid on /export/data/brick1/to_symlink failed
> 
> Which is what the linkat describes: if not giving AT_SYMLINK_FOLLOW flag some file system will report this. 
> 
> I haven’t tried with another filesystem yet, but OpenZFS is a possibility. I was just wondering if anyone already tried that? 
> 
> Just for the fun of it I build without using the linkat but the regular link. Now the link above succeed but it will be a hardlink to the target of the symlink. 
> 
> So the attempt to get the READLINK fails: 
> 
> [2015-02-28 10:20:27.934944] W [posix-handle.c:730:posix_handle_hard] 0-repl-posix: mismatching ino/dev between file /export/data/brick1/to_symlink (28617302/16777221) and handle /export/data/brick1/.glusterfs/04/87/048787fc-0d99-4927-8ef1-357f56fe84ae (28141430/16777221)
> [2015-02-28 10:20:27.935036] E [posix.c:1796:posix_symlink] 0-repl-posix: setting gfid on /export/data/brick1/to_symlink failed
> [2015-02-28 10:20:30.225177] E [posix.c:1038:posix_readlink] 0-repl-posix: readlink on /export/data/brick1/.glusterfs/04/87/048787fc-0d99-4927-8ef1-357f56fe84ae failed: Invalid argument
> [2015-02-28 10:20:30.225244] I [server-rpc-fops.c:1641:server_readlink_cbk] 0-repl-server: 139132: READLINK /to_symlink (048787fc-0d99-4927-8ef1-357f56fe84ae) ==> (Invalid argument)
> 
> This fails because glusterfs tries to readlink on a regular file. I will try to analyse a bit more to see if there could be a work-around
> 
> cheers,
> :-Dennis
> 
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20150301/1047a76d/attachment.html>