http://bugzilla.opensuse.org/show_bug.cgi?id=1144782
http://bugzilla.opensuse.org/show_bug.cgi?id=1144782#c12
--- Comment #12 from Ulrich Windl
This is the default config when using when installing Leap15.1 using snapper snapshots / rollback:
linux-wfhj:~ # cat /etc/fstab UUID=e637ab3e-e230-47ea-9f43-66f02385aaf7 / btrfs defaults 0 0 [...] linux-wfhj:~ # btrfs subvolume get-default / ID 268 gen 174 top level 267 path @/.snapshots/1/snapshot
Here I have (the latest snapshot has #67, however) ID 256 gen 2418 top level 5 path @
linux-wfhj:~ # btrfs subvolume delete /.snapshots/1/snapshot Delete subvolume (no-commit): '/.snapshots/1/snapshot' ERROR: Could not destroy subvolume/snapshot: Operation not permitted
linux-wfhj:~ # mount | grep snapshots /dev/vda2 on / type btrfs (rw,relatime,space_cache,subvolid=268,subvol=/@/.snapshots/1/snapshot) /dev/vda2 on /.snapshots type btrfs (rw,relatime,space_cache,subvolid=267,subvol=/@/.snapshots) linux-wfhj:~ #
I have /dev/mapper/sys-root on /.snapshots type btrfs (rw,relatime,space_cache,subvolid=274,subvol=/@/.snapshots) which is different.
So the root-fs is mounted in the default subvolume which could be any subvolume and it not specified explicitly in the fstab entry but just the defaults are used.
SO, not sure how you removed the default snapshot, but seems if you removed it was not the default at that point somehow.
I was using "rm -r".
At this point I'm not sure what the request is about, or what we should modify / fix at all.
Basically the request was that the filesystem filled up without finding put why, or what to do if it does. As I was unable to perform any useful work with the computer, I tried to fix things (which was the wrong way to do it.
BTW: I have involved Arvin as he is the expert in the area.
(In reply to Ulrich Windl from comment #3)
Anyway the filesystem after my recovery was only 44% filled, and currently (with about 15 snapshots) the filesystem is 55% filled.
Since then the filesystem filled to 66%, or about 5% (or almost 2GB) per month. Snapshots are (no idea where the gaps come from): # du -sh /.snapshots/[0-9]* 11G /.snapshots/1 11G /.snapshots/2 12G /.snapshots/3 11G /.snapshots/11 11G /.snapshots/12 11G /.snapshots/47 12G /.snapshots/48 12G /.snapshots/56 12G /.snapshots/57 12G /.snapshots/58 12G /.snapshots/59 12G /.snapshots/60 12G /.snapshots/61 12G /.snapshots/62 12G /.snapshots/63 12G /.snapshots/64 12G /.snapshots/65 12G /.snapshots/66 12G /.snapshots/67 These are the dates: # ll -d /.snapshots/[0-9]* drwxr-xr-x 1 root root 32 Aug 20 12:50 /.snapshots/1 drwxr-xr-x 1 root root 32 Aug 20 12:56 /.snapshots/2 drwxr-xr-x 1 root root 60 Aug 20 17:27 /.snapshots/3 drwxr-xr-x 1 root root 32 Aug 20 17:48 /.snapshots/11 drwxr-xr-x 1 root root 62 Aug 20 17:50 /.snapshots/12 drwxr-xr-x 1 root root 32 Oct 7 09:45 /.snapshots/47 drwxr-xr-x 1 root root 62 Oct 7 10:00 /.snapshots/48 drwxr-xr-x 1 root root 32 Oct 10 08:57 /.snapshots/56 drwxr-xr-x 1 root root 32 Oct 10 09:03 /.snapshots/57 drwxr-xr-x 1 root root 62 Oct 10 09:03 /.snapshots/58 drwxr-xr-x 1 root root 62 Oct 10 09:04 /.snapshots/59 drwxr-xr-x 1 root root 32 Oct 14 14:49 /.snapshots/60 drwxr-xr-x 1 root root 32 Oct 14 14:56 /.snapshots/61 drwxr-xr-x 1 root root 62 Oct 14 14:57 /.snapshots/62 drwxr-xr-x 1 root root 62 Oct 14 14:57 /.snapshots/63 drwxr-xr-x 1 root root 32 Oct 16 15:29 /.snapshots/64 drwxr-xr-x 1 root root 32 Oct 16 15:30 /.snapshots/65 drwxr-xr-x 1 root root 62 Oct 16 15:30 /.snapshots/66 drwxr-xr-x 1 root root 62 Oct 16 15:30 /.snapshots/67 -- You are receiving this mail because: You are on the CC list for the bug.