Hi Am Samstag, 2. Dezember 2023, 12:20:29 CET schrieb Philipp Storz: > Hello, > > Am 02.12.23 um 07:13 schrieb Jan Hebler: > > Hi > > > > Bareos does it's job very well, except that it not want to backup my > > container subvolumes, which are btrfs-subvolumes as well: > > > > .... > > 02-Dec 06:22 blaster-fd JobId 153: Disallowed filesystem. Will not > > descend from / into > > /srv/gitlab/.local/share/containers/storage/btrfs/subvolumes/253efabb1b8f > > 1d77d6e481a36fbd429c0a077583740fa548dca112d9516670ee > The subvolume seems to be of a different type than what you have specified > in your fileset. > > Probably it makes sense to set the debug level to 200 and enable tracing in > the filedaemon. > > -> setdebug trace=1 level=200 client=<your-client-fd> > > That should tell you the exact reason in the trace file. > > see: > https://github.com/bareos/bareos/blob/master/core/src/findlib/find_one.cc#L > 111-L121 > > .... > >
I think this points me in the correct direction. According to https://btrfs.readthedocs.io/en/latest/Subvolumes.html, btrfs subvolumes can, but does not need to be mounted like a "normal" Filesystem, but have their own dev-id anyway. This seems to confuse bareos, as (at least this is my understanding of https://github.com/bareos/bareos/blob/6f35a0436dd9e9428f100f28ea931fb37c2f3199/core/src/lib/mntent_cache.cc#L227-L237) bareos reads /proc/mounts into an cache and search for an entry for the device id afterwards. As the subvolumes is not explicit mounted, this fails. Regards, Jan -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/1918270.taCxCBeP46%40esmeralda.
signature.asc
Description: This is a digitally signed message part.
