[SOLVED] btrfs subvolume created at each boot (tmpfiles.d)

[sdauth]

Hello,
This is my btrfs root with a bunch of subvolume.

Code: Select all

ID 260 gen 194070 top level 5 path root
ID 261 gen 194070 top level 5 path home
ID 262 gen 194035 top level 5 path data
ID 263 gen 194034 top level 5 path swap
ID 265 gen 194054 top level 5 path snapshots
ID 472 gen 189965 top level 265 path snapshots/root.20260222T0631
ID 473 gen 189964 top level 265 path snapshots/home.20260222T0631

ID 480 gen 194058 top level 260 path root/srv

I never created root/srv subvolume (ID 480) but it is auto created (!) at every boot of my machine,
I removed it and it is created again automatically, what is going on ?
It started right after the upgrade of sys-apps/systemd-utils-259.3
I don't know if it is related or not but in /usr/lib/tmpfiles.d/home.conf ; I read :

Code: Select all

q /srv 0755 - - -

This is a new conf file too,

Code: Select all

sys-apps/systemd-utils-255.18
  if use tmpfiles; then
    doins tmpfiles.d/{etc,static-nodes-permissions,var}.conf

Code: Select all

sys-apps/systemd-utils-259.3
  if use tmpfiles; then
    installx usr/lib/tmpfiles.d/{etc,home,static-nodes-permissions,var}.conf

Any help appreciated. Thanks.

[sdauth]

if I comment it :

Code: Select all

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

# See tmpfiles.d(5) for details.

#Q /home 0755 - - -
#q /srv 0755 - - -

Then no more subvolume is created after a reboot so it seems there is something wrong with systemd-utils. I don't even have a /srv mountpoint anymore in / or any /srv active mountpoint (all commented) in fstab or /etc/exports (nfs) for example so why would a subvolume be created automatically ?

Is there a way to prevent this ? Or should I add another line in INSTALL_MASK to prevent /usr/lib/tmpfiles.d/home.conf from being installed to begin with ?

[sdauth]

Reading the doc:

Code: Select all

Files in /etc/tmpfiles.d override files with the same name in /usr/lib/tmpfiles.d

so:

Code: Select all

touch /etc/tmpfiles.d/home.conf

Works fine too. (and will survive to an update of systemd-utils)

I have no need for this feature so I'm marking this thread as solved.

[floppymaster]

tmpfiles.d(5) suggests using a symlink to /dev/null.

If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in /etc/tmpfiles.d/ bearing the same filename.

[sdauth]

Thanks, I had only read the part at the top of the manual

[sdauth]

Otherwise, I downloaded and extracted the following stage3 and none of them have "/srv"

Code: Select all

stage3-amd64-openrc:
bin, boot, dev, etc, home, lib, lib64, media, mnt, opt, proc, root, run, sbin, sys, tmp, usr, var

stage3-amd64-openrc-splitusr:
bin, boot, dev, etc, home, lib, lib64, media, mnt, opt, proc, root, run, sbin, sys, tmp, usr, var

stage3-amd64-systemd:
bin, boot, dev, etc, home, lib, lib64, media, mnt, opt, proc, root, run, sbin, sys, tmp, usr, var

and all have /srv in home.conf:

Code: Select all

grep srv stage3-amd64-*/usr/lib/tmpfiles.d/home.conf
stage3-amd64-openrc-splitusr/usr/lib/tmpfiles.d/home.conf:q /srv 0755 - - -
stage3-amd64-openrc/usr/lib/tmpfiles.d/home.conf:q /srv 0755 - - -
stage3-amd64-systemd/usr/lib/tmpfiles.d/home.conf:q /srv 0755 - - -

Since it is not present on gentoo, this triggers the creation of a /srv subvolume as tmpfiles.d manual explains :

Code: Select all

#Type Path                                     Mode User Group Age         Argument
q     /subvolume-or-directory/to/create        mode user group cleanup-age -

Just to compare with a debian install (trixie)

Code: Select all

bin, boot, dev, etc, home, initrd.img, initrd.img.old, lib, lib64, media, mnt, opt, proc, root, run, sbin, srv, sys, tmp, usr, var,
vmlinuz, vmlinuz.old

As you can see, /srv exists and it is not a subvolume.

Code: Select all

grep -i srv debian-debootstrap/usr/lib/tmpfiles.d/home.conf 
q /srv 0755 - - -

Same file but since /srv exists, no subvolume creation is triggered.
Anyway, I'm not a big fan of subvolume appearing in my root like that so I'll keep using the symlink of home.conf to /dev/null.
Otherwise, I guess I could also just "mkdir /srv" too in order to not trigger subvolume creation
Anyway... Just in case it helps someone else using btrfs.
Cheers.