Btrfs subvolume error

Issues & Assistance
1

Hello.

Yesterday I rollback a btrfs snapshot follow this Restoring snapshots to get the system back to working state | Garuda Linux wiki

I notice this morning some error on the subvolume snapshot and snapshot not working anymore

System:
  Kernel: 5.15.31-1-lts arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
    root=UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 rw rootflags=subvol=@
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3
  Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.29 info: xfce4-panel, plank
    wm: xfwm v: 4.16.1 vt: 7 dm: LightDM v: 1.30.0 Distro: Garuda Linux
    base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME H510M-A v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 1017
    date: 07/12/2021
CPU:
  Info: model: Intel Core i5-10400F bits: 64 type: MT MCP arch: Comet Lake
    family: 6 model-id: 0xA5 (165) stepping: 3 microcode: 0xEC
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 800 min/max: 800/4300 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 69597
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 status: Vulnerable: eIBRS with unprivileged eBPF
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GA106 [Geforce RTX 3050] vendor: Gigabyte driver: nvidia
    v: 510.54 alternate: nouveau,nvidia_drm pcie: gen: 1 speed: 2.5 GT/s
    lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:2507 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 compositor: xfwm v: 4.16.1 driver:
    X: loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
    gpu: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26")
    s-diag: 583mm (22.95")
  Monitor-1: HDMI-1 res: 1920x1080 hz: 60 dpi: 94
    size: 521x293mm (20.51x11.54") diag: 598mm (23.53") modes: N/A
  OpenGL: renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2
    v: 4.6.0 NVIDIA 510.54 direct render: Yes
Audio:
  Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:f0c8 class-ID: 0403
  Device-2: NVIDIA vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
    gen: 3 speed: 8 GT/s lanes: 8 link-max: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:228e class-ID: 0403
  Sound Server-1: ALSA v: k5.15.31-1-lts running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15fa class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 566.37 GiB used: 343.74 GiB (60.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: A-Data model: SX6000NP
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B
    speed: 15.8 Gb/s lanes: 2 type: SSD serial: <filter> rev: V6005-af
    temp: 40.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT480BX500SSD1
    size: 447.13 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 054 scheme: GPT
Partition:
  ID-1: / raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 23.86 GiB (20.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 23.86 GiB (20.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 23.86 GiB (20.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 118.95 GiB size: 118.95 GiB (100.00%)
    used: 23.86 GiB (20.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 15.48 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A gpu: nvidia temp: 47 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 319 Uptime: 24m wakeups: 0 Memory: 15.48 GiB
  used: 2.33 GiB (15.1%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.2.0 Packages: pacman: 1466 lib: 496 Shell: Zsh v: 5.8.1
  running-in: xfce4-terminal inxi: 3.3.14
Garuda (2.5.6-2):
  System install date:     2022-03-18
  Last full system update: 2022-03-26
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Snapper
  Failed units:

Some log

sudo tail -F /var/log/snapper.log
MIL libsnapper(2045) AsciiFile.cc(getValue):242 - key:QGROUP value:
MIL libsnapper(2045) AsciiFile.cc(getValue):242 - key:SYNC_ACL value:no
MIL libsnapper(2045) Snapper.cc(Snapper):125 - subvolume:/ filesystem:btrfs
MIL libsnapper(2045) Snapper.cc(loadIgnorePatterns):195 - number of ignore patterns:8
WAR libsnapper(2045) Btrfs.cc(openInfosDir):266 - THROW: .snapshots is not a btrfs subvolume
ERR libsnapper(2045) Snapshot.cc(initialize):364 - reading failed
WAR libsnapper(2045) Btrfs.cc(openInfosDir):266 - THROW: .snapshots is not a btrfs subvolume
WAR libsnapper(2045) Client.cc(dispatch):1830 - CAUGHT: .snapshots is not a btrfs subvolume
MIL libsnapper(2045) Snapper.cc(~Snapper):137 - Snapper destructor
MIL libsnapper(2045) snapperd.cc(main):308 - Exiting

sudo btrfs subvolume list /                      
ID 256 gen 440547 top level 5 path restore_backup_@_123533194
ID 257 gen 441741 top level 5 path @home
ID 258 gen 441714 top level 5 path @root
ID 259 gen 36 top level 5 path @srv
ID 260 gen 441629 top level 5 path @cache
ID 261 gen 441741 top level 5 path @log
ID 262 gen 441717 top level 5 path @tmp
ID 263 gen 440554 top level 256 path restore_backup_@_123533194/.snapshots
ID 473 gen 439913 top level 263 path restore_backup_@_123533194/.snapshots/1/snapshot
ID 474 gen 440169 top level 263 path restore_backup_@_123533194/.snapshots/2/snapshot
ID 475 gen 440170 top level 263 path restore_backup_@_123533194/.snapshots/3/snapshot
ID 476 gen 440434 top level 263 path restore_backup_@_123533194/.snapshots/4/snapshot
ID 477 gen 440435 top level 263 path restore_backup_@_123533194/.snapshots/5/snapshot
ID 478 gen 440439 top level 263 path restore_backup_@_123533194/.snapshots/6/snapshot
ID 479 gen 440558 top level 263 path restore_backup_@_123533194/.snapshots/7/snapshot
ID 480 gen 440520 top level 263 path restore_backup_@_123533194/.snapshots/8/snapshot
ID 481 gen 440521 top level 263 path restore_backup_@_123533194/.snapshots/9/snapshot
ID 482 gen 441741 top level 5 path @

I am able to remount the volume

sudo mount -o subvol=@ /dev/nvme0n1p2 /.snapshots

This add this subvolume
ID 486 gen 441697 top level 482 path 1/snapshot
But if I reboot I need to re mount the subvolume each time and seems not fully working because if i reboot in restoration mode I only see the snapshot on this subvolume
restore_backup_@_123533194/.snapshots

Have a nice day

2

What does the error say?

Have you examined /etc/fstab?

3

See log in previous message

WAR libsnapper(2045) Btrfs.cc(openInfosDir):266 - THROW: .snapshots is not a btrfs subvolume
ERR libsnapper(2045) Snapshot.cc(initialize):364 - reading failed
WAR libsnapper(2045) Btrfs.cc(openInfosDir):266 - THROW: .snapshots is not a btrfs subvolume
WAR libsnapper(2045) Client.cc(dispatch):1830 - CAUGHT: .snapshots is not a btrfs subvolume

fstab is like this

UUID=36C8-F8BD                            /boot/efi      vfat    umask=0077 0 2
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /              btrfs   subvol=/@,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /home          btrfs   subvol=/@home,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /root          btrfs   subvol=/@root,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /srv           btrfs   subvol=/@srv,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /var/cache     btrfs   subvol=/@cache,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /var/log       btrfs   subvol=/@log,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /var/tmp       btrfs   subvol=/@tmp,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

May I need to add an entry in fstab like this ?

UUID=ece8ff72-3221-4048-b7f2-fb09c55ff932 /              btrfs   subvol=/@snapshot,defaults,noatime,autodefrag,compress=zstd,discard=async,ssd 0 0
4

I am hesitant to weigh in on this because I am actually not certain what the answer is. I started to look for a concise answer but I got in the weeds a little bit.

My first instinct was to advise against this, because I have a few Garuda installs and none of them contain this entry.

But after looking into it, I’m starting to think this is a reasonable solution. See this old discussion: Can't snapshot anymore after a "snapper rollback" · Issue #159 · openSUSE/snapper · GitHub

See also this from Snapper documentation: Snapper, The ultimate Snapshot Tool for Linux

I’m hoping we’ll have an expert weigh in and clarify for us.

5

Thanks you that help me to figure it out
So I re install Garuda on another nvme I've got
I take some information after fresh install on btrfs subvolumes
And I think I've got it
First command error is expected

sudo btrfs subvolume delete /.snapshots
ERROR: Not a Btrfs subvolume: Invalid argument
zsh: exit 1     sudo btrfs subvolume delete /.snapshots 

sudo rm -rf /.snapshots                
sudo btrfs subvolume create /.snapshots
Create subvolume '//.snapshots'

After this go to btrfs assistant and create a manually snapshot work as expected

EDIT : after reboot it's ok too
But I need to do some clean up I've always the old shit

ID 263 gen 442182 top level 256 path restore_backup_@_123533194/.snapshots
ID 473 gen 439913 top level 263 path restore_backup_@_123533194/.snapshots/1/snapshot
ID 474 gen 440169 top level 263 path restore_backup_@_123533194/.snapshots/2/snapshot
ID 475 gen 440170 top level 263 path restore_backup_@_123533194/.snapshots/3/snapshot
ID 476 gen 440434 top level 263 path restore_backup_@_123533194/.snapshots/4/snapshot
ID 477 gen 440435 top level 263 path restore_backup_@_123533194/.snapshots/5/snapshot
ID 478 gen 440439 top level 263 path restore_backup_@_123533194/.snapshots/6/snapshot
ID 479 gen 440558 top level 263 path restore_backup_@_123533194/.snapshots/7/snapshot
ID 480 gen 440520 top level 263 path restore_backup_@_123533194/.snapshots/8/snapshot
ID 481 gen 440521 top level 263 path restore_backup_@_123533194/.snapshots/9/snapshot
ID 491 gen 442133 top level 482 path 6/snapshot
ID 492 gen 442200 top level 482 path 7/snapshot
ID 493 gen 442201 top level 482 path 8/snapshot

Thanks to this I stay away from add entry in fstab for snapshot mountpoint

6

No no, that's not right, you screwed this up pretty bad >.>

Please just do update remote reset-snapper and avoid messing with BTRFS stuff manually unless you know what you're doing.

3 Likes
7

Thanks for your reply
You're absolutely right
I notice some error in

/var/log/snapper.log 
2022-03-27 11:22:47 MIL libsnapper(13634) AsciiFile.cc(getValue):242 - key:FSTYPE value:btrfs
2022-03-27 11:22:47 MIL libsnapper(13634) AsciiFile.cc(getValue):242 - key:QGROUP value:
2022-03-27 11:22:47 MIL libsnapper(13634) AsciiFile.cc(getValue):242 - key:SYNC_ACL value:no
2022-03-27 11:22:47 MIL libsnapper(13634) Snapper.cc(Snapper):125 - subvolume:/ filesystem:btrfs
2022-03-27 11:22:47 MIL libsnapper(13634) Snapper.cc(loadIgnorePatterns):195 - number of ignore patterns:8
2022-03-27 11:22:47 MIL libsnapper(13634) Snapshot.cc(read):274 - found 2 snapshots
2022-03-27 11:22:56 WAR libsnapper(13634) FileUtils.cc(SDir):91 - THROW: open failed path://.snapshots/1 errno:2 (No such file or directory)
2022-03-27 11:22:56 WAR libsnapper(13634) Btrfs.cc(checkSnapshot):481 - CAUGHT: open failed path://.snapshots/1 errno:2 (No such file or directory)
2022-03-27 11:23:26 MIL libsnapper(13634) Snapper.cc(~Snapper):137 - Snapper destructor
2022-03-27 11:23:56 MIL libsnapper(13634) snapperd.cc(main):308 - Exiting

I apply your command
That make some clean up

update remote reset-snapper            
Delete subvolume (no-commit): '//restore_backup_@_123533194/.snapshots/1/snapshot'
Delete subvolume (no-commit): '//restore_backup_@_123533194/.snapshots/2/snapshot'
Delete subvolume (no-commit): '//restore_backup_@_123533194/.snapshots/3/snapshot'
Delete subvolume (no-commit): '//restore_backup_@_123533194/.snapshots/4/snapshot'
Delete subvolume (no-commit): '//restore_backup_@_123533194/.snapshots/5/snapshot'
Delete subvolume (no-commit): '//restore_backup_@_123533194/.snapshots/6/snapshot'
Delete subvolume (no-commit): '//restore_backup_@_123533194/.snapshots/7/snapshot'
Delete subvolume (no-commit): '//restore_backup_@_123533194/.snapshots/8/snapshot'
Delete subvolume (no-commit): '//restore_backup_@_123533194/.snapshots/9/snapshot'
Delete subvolume (no-commit): '//restore_backup_@_123533194/.snapshots'
Delete subvolume (no-commit): '//restore_backup_@_123533194'
Delete subvolume (no-commit): '//@/.snapshots/1/snapshot'
Delete subvolume (no-commit): '//@/.snapshots'
rm: impossible de supprimer '/.snapshots/': Aucun fichier ou dossier de ce type
zsh: exit 1     update remote reset-snapper

sudo btrfs subvolume list /
ID 257 gen 444051 top level 5 path @home
ID 258 gen 444051 top level 5 path @root
ID 259 gen 36 top level 5 path @srv
ID 260 gen 442922 top level 5 path @cache
ID 261 gen 444051 top level 5 path @log
ID 262 gen 443297 top level 5 path @tmp
ID 482 gen 444051 top level 5 path @
ID 491 gen 442133 top level 482 path 6/snapshot
ID 492 gen 442200 top level 482 path 7/snapshot
ID 493 gen 442201 top level 482 path 8/snapshot

But now in btrfs assistant I not able to make snapshot anymore
That's delete config
"No config selected for snapshot"
I'm not able to create root config

2022-03-27 18:28:33 MIL libsnapper(19290) Snapper.cc(createConfig):331 - Snapper create-config
2022-03-27 18:28:33 MIL libsnapper(19290) Snapper.cc(createConfig):332 - libsnapper version 0.9.1
2022-03-27 18:28:33 MIL libsnapper(19290) Snapper.cc(createConfig):333 - config_name:root subvolume:/ fstype:btrfs template_name:default
2022-03-27 18:28:33 MIL libsnapper(19290) Snapper.cc(getConfigs):290 - Snapper get-configs
2022-03-27 18:28:33 MIL libsnapper(19290) Snapper.cc(getConfigs):291 - libsnapper version 0.9.1
2022-03-27 18:28:33 MIL libsnapper(19290) AsciiFile.cc(reload):115 - loading file /etc/conf.d/snapper
2022-03-27 18:28:33 MIL libsnapper(19290) AsciiFile.cc(getValue):242 - key:SNAPPER_CONFIGS value:root
2022-03-27 18:28:33 MIL libsnapper(19290) AsciiFile.cc(reload):115 - loading file /etc/snapper/configs/root
2022-03-27 18:28:33 WAR libsnapper(19290) AsciiFile.cc(AsciiFileReader):67 - open for '/etc/snapper/configs/root' failed
2022-03-27 18:28:33 WAR libsnapper(19290) AsciiFile.cc(AsciiFileReader):68 - THROW: file not found
2022-03-27 18:28:33 ERR libsnapper(19290) Snapper.cc(getConfigs):309 - config 'root' not found
2022-03-27 18:28:33 MIL libsnapper(19290) AsciiFile.cc(reload):115 - loading file /etc/conf.d/snapper
2022-03-27 18:28:33 MIL libsnapper(19290) AsciiFile.cc(getValue):242 - key:SNAPPER_CONFIGS value:root
2022-03-27 18:28:33 WAR libsnapper(19290) Snapper.cc(createConfig):387 - THROW: config already exists
2022-03-27 18:28:33 WAR libsnapper(19290) Client.cc(dispatch):1752 - CAUGHT: config already exists

sudo cat /etc/conf.d/snapper
## Path: System/Snapper

## Type:        string
## Default:     ""
# List of snapper configurations.
SNAPPER_CONFIGS="root"

I remove
SNAPPER_CONFIGS="root"
to
SNAPPER_CONFIGS=""

Recreate from btrfs assistant and seems good
But when I make I snapshoot I can see in btrfs assistant and restore mode BUT I've got this

2022-03-27 18:31:24 MIL libsnapper(19475) Snapper.cc(Snapper):92 - Snapper constructor
2022-03-27 18:31:24 MIL libsnapper(19475) Snapper.cc(Snapper):93 - libsnapper version 0.9.1
2022-03-27 18:31:24 MIL libsnapper(19475) Snapper.cc(Snapper):94 - config_name:root disable_filters:false
2022-03-27 18:31:24 MIL libsnapper(19475) AsciiFile.cc(reload):115 - loading file /etc/snapper/configs/root
2022-03-27 18:31:24 MIL libsnapper(19475) AsciiFile.cc(getValue):242 - key:SUBVOLUME value:/
2022-03-27 18:31:24 MIL libsnapper(19475) AsciiFile.cc(getValue):242 - key:FSTYPE value:btrfs
2022-03-27 18:31:24 MIL libsnapper(19475) AsciiFile.cc(getValue):242 - key:QGROUP value:
2022-03-27 18:31:24 MIL libsnapper(19475) AsciiFile.cc(getValue):242 - key:SYNC_ACL value:no
2022-03-27 18:31:24 MIL libsnapper(19475) Snapper.cc(Snapper):125 - subvolume:/ filesystem:btrfs
2022-03-27 18:31:24 MIL libsnapper(19475) Snapper.cc(loadIgnorePatterns):195 - number of ignore patterns:8
2022-03-27 18:31:24 MIL libsnapper(19475) Snapshot.cc(read):274 - found 2 snapshots
2022-03-27 18:31:43 WAR libsnapper(19475) FileUtils.cc(SDir):91 - THROW: open failed path://.snapshots/2 errno:2 (No such file or directory)
2022-03-27 18:31:43 WAR libsnapper(19475) Btrfs.cc(checkSnapshot):481 - CAUGHT: open failed path://.snapshots/2 errno:2 (No such file or directory)


 sudo ls -al /.snapshots
total 0
drwxr-x--- 1 root root   2 27 mars  18:32 .
drwxr-xr-x 1 root root 174 27 mars  18:20 ..
drwxr-xr-x 1 root root  32 27 mars  18:32 1

sudo ls -al /.snapshots/1/
total 4
drwxr-xr-x 1 root root  32 27 mars  18:32 .
drwxr-x--- 1 root root   2 27 mars  18:32 ..
-rw------- 1 root root 162 27 mars  18:32 info.xml
drwxr-xr-x 1 root root 174 27 mars  18:20 snapshot

sudo ls -al /.snapshots/1/snapshot/
total 20
drwxr-xr-x 1 root root  174 27 mars  18:20 .
drwxr-xr-x 1 root root   32 27 mars  18:32 ..
drwxr-xr-x 1 root root   32 26 mars  17:00 6
drwxr-xr-x 1 root root   32 26 mars  17:45 7
drwxr-xr-x 1 root root   60 26 mars  17:46 8
lrwxrwxrwx 1 root root    7  7 déc.  03:41 bin -> usr/bin
drwxr-xr-x 1 root root  208 24 mars  09:23 boot
drwxr-xr-x 1 root root    0 18 mars  10:40 dev
drwxr-xr-x 1 root root 4242 26 mars  20:06 etc
-rw-r--r-- 1 root root    7  8 mars  10:18 .garuda-tools
drwxr-xr-x 1 root root    0 18 mars  10:40 home
lrwxrwxrwx 1 root root    7  7 déc.  03:41 lib -> usr/lib
lrwxrwxrwx 1 root root    7  7 déc.  03:41 lib64 -> usr/lib
drwxr-xr-x 1 root root    0  7 déc.  03:41 mnt
drwxr-xr-x 1 root root   14 22 mars  13:52 opt
drwxr-xr-x 1 root root    0 18 mars  10:40 proc
drwxr-xr-x 1 root root    0 18 mars  10:40 root
drwxr-xr-x 1 root root    0 18 mars  10:40 run
lrwxrwxrwx 1 root root    7  7 déc.  03:41 sbin -> usr/bin
drwxr-xr-x 1 root root    0 27 mars  18:34 .snapshots
drwxr-xr-x 1 root root    0 18 mars  10:40 srv
drwxr-xr-x 1 root root    0 18 mars  10:40 sys
drwxrwxrwt 1 root root    0 18 mars  10:43 tmp
drwxr-xr-x 1 root root   80 26 mars  17:45 usr
drwxr-xr-x 1 root root  126 26 mars  17:47 var
8

I think this is solve my issue thanks you
But in this such case do I did something wrong when I rollback ?
May be add this do the documentation if it's needed after rollback entire / ?
But I've always this in btrfs subvolume I not able to delete this with your command
6/snapshot
7/snapshot
8/snapshot

ID 257 gen 446776 top level 5 path @home
ID 258 gen 446761 top level 5 path @root
ID 259 gen 36 top level 5 path @srv
ID 260 gen 446734 top level 5 path @cache
ID 261 gen 446776 top level 5 path @log
ID 262 gen 446686 top level 5 path @tmp
ID 482 gen 446776 top level 5 path @
ID 491 gen 442133 top level 482 path 6/snapshot
ID 492 gen 442200 top level 482 path 7/snapshot
ID 493 gen 442201 top level 482 path 8/snapshot
ID 498 gen 446677 top level 482 path .snapshots
ID 503 gen 446161 top level 498 path .snapshots/1/snapshot
ID 504 gen 446673 top level 498 path .snapshots/2/snapshot
ID 505 gen 446675 top level 498 path .snapshots/3/snapshot

ID 50X is the new created snashots
Thanks again for your help

1 Like
9

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.