Re: [Bacula-users] bacula and glusterfs

[Martin S. <ma...@li...>]

>>>>> 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 filesystems mounted elsewhere -- in this
> case, /gluster/home -- and /home on either node becomes a synchronized
> view of the union of /gluster/home from each node.  In my case, the
> contents are replicated over both nodes.)  The nodes are using the 
> glusterfs native client, not the NFS client.
> 
> 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 warnings
> in the backups:
> 
> 22-Dec 00:52 hostname.example.com-fd JobId 3691:      Could not open
> directory "/home/USERNAME": ERR=Operation not permitted
> 
> (There is currently only one user in /home)
> 
> The client is bacula-client-3.0.2-1.x86_64 (CentOS, fschwarz bacula build)
> 
> bacula-fd is running as user root, group bacula.
> 
> In a root shell (logged in as root, not via sudo), I can descend into
> that directory and read the contents and create new files, so it's not
> a root-squash issue AFAICT.
> 
> Before I go splunking through code, does anyone know if bacula-fd is
> doing any funky real/effective UID swapping during its lifecycle that
> may be influencing this?

No, It only switches UID on startup.


> Any other related information or suggestions are welcome.

Do you have SELinux running in enforcing mode?  If so, try switching it off
temporarily with /usr/sbin/setenforce 0.

__Martin