All HI systemdgroup, i found a special behavior with btrfs and systemd mount. BTRFS is partly diverting its "subvolume" technics from the functional intended usage: A "subvolume" is usable like an directory. The documentation indicates such possibility, also. E.g.: The User can replace the recursive delete command on directories with a btrfs command. https://www.oracle.com/technical-resources/articles/it-infrastructure/admin-advanced-btrfs.html Triggered by this suggestion i tried to use a btrfs subvolume as mount directory inside of an systemd mount unit. And, spring success on myself. Then, came a question into being. Appears a btrfs subvolume to the system mount service with the aspect of a directory, and btrfs subvolume features a not capable anymore? (Owing to, btrfs is falling back into a classical directory...) Or: both systems are lying next to each other without interference and with full feature set. E.g. snapshots with btrfs or changed directory mode through systemd after mounting. sincerely -kefko -- Wonderful vim doku: When a mapping triggers itself, it will run forever WEB www.johannes-koehler.de