On the brick server (the content server... the one with the XFS-formatted volume), FUSE is actually not used or even needed as far as I can tell. Leave your fstab mount alone, and treat GlusterFS as a pure replacement for NFS's /etc/exports. FUSE only comes into play on the client side, where it's no longer relevant what the underlying filesystem is. If I'm reading you right, your XServe is the client in this scenario. Perhaps Mac OSX's FUSE implementation is strange somehow, I'm not familiar with it. Otherwise, it sounds to me like you're doing it right. Sounds like either a permissions problem or a bug somewhere (first guesses would be Mac OSX's FUSE, or GlusterFS client on OSX). On Thu, Jan 1, 2009 at 11:55 PM, admin@xxxxxxxxxxx <admin@xxxxxxxxxxx> wrote: > Dear All, > > I'm afraid I'm a bit new to this. I hope I'm not missing the obvious, but in > all the documentation I can't seem to find a clear answer to my problem. > > I have a head server (Leopard X serve) that will be used as a mount point > for four sub-servers (Debian Etch) that each have two SATA RAID 5 blocks > running an XFS filesystem. > > Before I switched to glusterfs, I would do an NFS export (/etc/exports) of > the XFS filesystem mounted in /etc/fstab. I have since cancelled (commented > out) the NFS export, but I am not quite sure what to do about the fstab: > Should I mount the drives using this file, then export the filesystem using > glusterfs? Or should it be glusterfs doing the mounting? What role does FUSE > have in the mount operation? > > The RAID drives are at /dev/sdb and /dev/sdc, and their filesystems are > accessible at /dev/sdb1 and /dev/sdc1 - should I be mounting these with > glusterfs (instead of mounting them to a folder in the server root as I am > doing presently)? > > With my present configuration, all works correctly if I mount the raid > drives individually, yet when I mirror two drives across two servers using > AFS things get wonky - I can upload files to a folder (and see that they > have indeed been replicated to both drives), yet I am unable to create a new > folder (it becomes an inaccessible icon). > > Thank you for any advice. > > Best, > > J.M. Schomburg. > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxx > http://lists.nongnu.org/mailman/listinfo/gluster-devel >
