On Wed, 29 Dec 2010 19:22:55 -0700, Devin Reade said:
Martin Simmons mar...@lispworks.com wrote:
I read that glusterfs uses FUSE, so it might be checking something more than
the uid. That would explain why a root shell can access the files. Note
that
the error is Operation not
Martin Simmons mar...@lispworks.com wrote:
I read that glusterfs uses FUSE, so it might be checking something more than
the uid. That would explain why a root shell can access the files. Note that
the error is Operation not permitted, which is different from the normal
Permission denied
On Sat, 25 Dec 2010 10:39:45 -0700, Devin Reade said:
Martin Simmons mar...@lispworks.com wrote:
On Wed, 22 Dec 2010 14:09:50 -0700, Devin Reade said:
I have set up bacula clients on these nodes and, in addition to the
usual ext3 filesystems (/, /usr, et cetera), I'm trying to back
Martin Simmons mar...@lispworks.com wrote:
On Wed, 22 Dec 2010 14:09:50 -0700, Devin Reade said:
I have set up bacula clients on these nodes and, in addition to the
usual ext3 filesystems (/, /usr, et cetera), I'm trying to back up
the glusterfs-mounted /home, however I'm seeing the current
On Wed, 22 Dec 2010 14:09:50 -0700, Devin Reade said:
Yes, this is bacula related, but first some background.
I've got a new two-node HA cluster where I am trying the new (for me)
mechanism of using glusterfs for /home. (For anyone not familiar with
this, both nodes have native
Yes, this is bacula related, but first some background.
I've got a new two-node HA cluster where I am trying the new (for me)
mechanism of using glusterfs for /home. (For anyone not familiar with
this, both nodes have native filesystems mounted elsewhere -- in this
case, /gluster/home -- and
