Re: [Bacula-users] Bacula 7.4.4: Strange warnings non-existent filesystem crossings

2016-10-16 Thread Andreas Koch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here's a brief update on this issue: After taking the automounter out of the equation, and hard-mounting all file systems, the last differential did not show the spurious warnings on crossing file-system boundaries. Whether the Accurate differential

Re: [Bacula-users] Bacula 7.4.4: Strange warnings non-existent filesystem crossings

2016-10-14 Thread Andreas Koch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/14/2016 05:31 PM, Hankins, Jonathan wrote: > I'm not really familiar with EMC's NFS, NFSv4 and automounter, but here's > a shot in the dark - what do your export and mount options look like? In > particular, look into nohide or crossmnt export

Re: [Bacula-users] Bacula 7.4.4: Strange warnings non-existent filesystem crossings

2016-10-14 Thread Hankins, Jonathan
I'm not really familiar with EMC's NFS, NFSv4 and automounter, but here's a shot in the dark - what do your export and mount options look like? In particular, look into nohide or crossmnt export options. Also, have a look at this:

[Bacula-users] Bacula 7.4.4: Strange warnings non-existent filesystem crossings

2016-10-14 Thread Andreas Koch
Hello all, we have observed strange behavior in our recent backups. We have a number of filesystems, and explicitly list those to be backed up in the fileset One of these file systems is /home/stud which has subdirectories for each user. Backing these up has worked perfectly for the