On Mon, Jul 8, 2019 at 3:02 PM Ulli Horlacher <frams...@rus.uni-stuttgart.de> wrote: ... > > root@trulla:/# btrfs subvolume get-default / > ID 453 gen 2273956 top level 270 path @/.snapshots/128/snapshot > > root@trulla:/# btrfs subvolume show / | grep UUID > UUID: c85dc50a-b126-1441-bddd-2832afac58d2 > Parent UUID: d2f6c896-ff9a-2f4c-b60f-7d0e20ab834c > > > parent_uuid d2f6c896-ff9a-2f4c-b60f-7d0e20ab834c uuid > c85dc50a-b126-1441-bddd-2832afac58d2 path @/.snapshots/128/snapshot > > All (snapper) snapshots have @/.snapshots/128/snapshot as parent which is > the default / subvolme > But what/where is subvolume with UUID d2f6c896-ff9a-2f4c-b60f-7d0e20ab834c? > Was it the installation subvolume which has been deleted afterwards? >
Immediately after installation default subvolume (your root) should have been @/.snapshots/1/snapshot. Most likely at some point "snap revert" was performed on this system which changed root to another clone. Then original root aged off. > The subvolume @ is not default mounted - why? And why should it be? It is rather questionable whether this subvolume is needed at all. I do not think it is created in current openSUSE or SLES15. > It uses disk space (/lib /lib64 ...) but it does not get updated? > > root@trulla:/# l -Rrt /mnt/_/@/lib/ | grep -v ^d|tail -3 > -RW- 573,168 2015-09-24 12:16 > /mnt/_/@/lib/modules/3.12.44-52.18-default/modules.alias.bin > -RW- 603,413 2015-09-24 12:16 > /mnt/_/@/lib/modules/3.12.44-52.18-default/modules.alias > l--- - 2015-09-24 12:16 > /mnt/_/@/lib/modules/3.12.44-52.18-default/weak-updates/updates/crash.ko -> > /lib/modules/3.12.28-4-default/updates/crash.ko > > root@trulla:/# l -Rrt /lib/ | grep -v ^d|tail -3 > -RW- 680,805 2019-06-18 11:42 > /lib/modules/4.4.180-94.97-default/modules.alias.bin > -RW- 723,956 2019-06-18 11:42 > /lib/modules/4.4.180-94.97-default/modules.alias > lRW- - 2019-06-18 11:42 > /lib/modules/4.4.180-94.97-default/weak-updates/updates/crash.ko -> > /lib/modules/4.4.175-94.79-default/updates/crash.ko > > So, it uses disk space, which cannot be freed? > And how it is related to upstream btrfs? Open SUSE bug report (or actually support request as you have SUSE and not openSUSE).
