Cannot install or update via zypper dup or YaST
Please let me know what system information you need to be able to help.
Thank you for the help
# zypper dup
The target filesystem is mounted as read-only. Please make sure the target filesystem is writeable.
Is the root file system full?
Check the output of
df /
If you are using “btrfs” (likely), then check the output of:
btrfs filesystem df /
df /
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 41975640 19893480 21729816 48% /
btrfs filesystem df /
Data, single: total=21.01GiB, used=17.74GiB
System, DUP: total=32.00MiB, used=16.00KiB
Metadata, DUP: total=768.00MiB, used=610.91MiB
GlobalReserve, single: total=35.09MiB, used=0.00B
And of course check if there are any file systems mounted read-only
mount
This is the first time I have installed with btrfs.
There are some things I am not familiar with.
If there is anything that needs to change, please let me know.
mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,noexec,size=4023064k,nr_inodes=1005766,mode=755,inode64)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=1613712k,nr_inodes=819200,mode=755,inode64)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755,inode64)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
/dev/sda3 on / type btrfs (ro,relatime,space_cache,subvolid=266,subvol=/@/.snapshots/1/snapshot)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=17202)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,nr_inodes=409600,inode64)
/dev/sda3 on /.snapshots type btrfs (ro,relatime,space_cache,subvolid=265,subvol=/@/.snapshots)
/dev/sdc2 on /linux-back9-LXQT type btrfs (rw,relatime,ssd,space_cache,subvolid=256,subvol=/@)
/dev/sdc2 on /linux-back9-LXQT/boot/grub2/i386-pc type btrfs (rw,relatime,ssd,space_cache,subvolid=258,subvol=/@/boot/grub2/i386-pc)
/dev/sdc2 on /linux-back9-LXQT/opt type btrfs (rw,relatime,ssd,space_cache,subvolid=263,subvol=/@/opt)
/dev/sdc2 on /linux-back9-LXQT/boot/grub2/x86_64-efi type btrfs (rw,relatime,ssd,space_cache,subvolid=257,subvol=/@/boot/grub2/x86_64-efi)
/dev/sdc2 on /linux-back9-LXQT/srv type btrfs (rw,relatime,ssd,space_cache,subvolid=261,subvol=/@/srv)
/dev/sdc2 on /linux-back9-LXQT/usr/local type btrfs (rw,relatime,ssd,space_cache,subvolid=260,subvol=/@/usr/local)
/dev/sdc2 on /linux-back9-LXQT/var type btrfs (rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/var)
/dev/sdc2 on /linux-back9-LXQT/root type btrfs (rw,relatime,ssd,space_cache,subvolid=262,subvol=/@/root)
/dev/sda3 on /boot/grub2/x86_64-efi type btrfs (ro,relatime,space_cache,subvolid=263,subvol=/@/boot/grub2/x86_64-efi)
/dev/sda3 on /srv type btrfs (ro,relatime,space_cache,subvolid=260,subvol=/@/srv)
/dev/sda3 on /root type btrfs (ro,relatime,space_cache,subvolid=261,subvol=/@/root)
/dev/sda3 on /usr/local type btrfs (ro,relatime,space_cache,subvolid=259,subvol=/@/usr/local)
/dev/sda3 on /var type btrfs (ro,relatime,space_cache,subvolid=258,subvol=/@/var)
/dev/sda3 on /opt type btrfs (ro,relatime,space_cache,subvolid=262,subvol=/@/opt)
/dev/sda3 on /boot/grub2/i386-pc type btrfs (ro,relatime,space_cache,subvolid=264,subvol=/@/boot/grub2/i386-pc)
/dev/sdc1 on /windows-D type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sdb1 on /home type ext4 (rw,relatime,data=ordered)
/dev/sdb2 on /backups type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
/dev/sda1 on /windows-C type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=806856k,nr_inodes=201714,mode=700,uid=1000,gid=100,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
This one:
/dev/sda3 on / type btrfs (**ro**,relatime,space_cache,subvolid=266,subvol=/@/.snapshots/1/snapshot)
But why? So YaST is only reporting the truth and of course can not write to a ro file sytem
I am no Btrfs user. But looking in the logs might help. Maybe browse through
dmesg
zypper tells all. Check your journal and post the output of: ‘journalctl -b --grep btrfs’.
Some 3 GiB free may not be enough for a “zypper dup”, then the system went read-only to avoid corruption?
Maybe deleting some snapshots might fix things.
journalctl -b --grep btrfs
An error was encountered while opening journal file or directory /var/log/journal/bc10c50387c1432d9d156b75d0632527/user-1000@4f3fafb1534243adb22a06ddd4de7597-0000000000009680-0005b7cba0016030.journal, ignoring file: Input/output error
-- Logs begin at Tue 2020-11-17 19:00:38 CST, end at Fri 2021-01-01 00:29:07 CST. --
Dec 29 09:30:51 localhost dracut-cmdline[181]: Using kernel command line parameters: rd.driver.pre=btrfs root=UUID=14c5d68e-7778-48e8-adb7-4c164d951>
Dec 29 09:30:52 localhost kernel: Btrfs loaded, crc32c=crc32c-generic, assert=on
Dec 29 09:30:54 localhost kernel: BTRFS: device label LXQT devid 1 transid 549 /dev/sdc2 scanned by systemd-udevd (276)
Dec 29 09:30:54 localhost kernel: BTRFS: device label Cinnamon devid 1 transid 78936 /dev/sda3 scanned by systemd-udevd (256)
Dec 29 09:30:55 localhost kernel: BTRFS info (device sda3): disk space caching is enabled
Dec 29 09:30:55 localhost kernel: BTRFS info (device sda3): has skinny extents
Dec 29 09:30:55 localhost kernel: BTRFS info (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 22, gen 0
Dec 29 15:31:00 localhost kernel: BTRFS info (device sda3): disk space caching is enabled
Dec 29 15:31:01 localhost kernel: BTRFS info (device sdc2): disk space caching is enabled
Dec 29 15:31:01 localhost kernel: BTRFS info (device sdc2): has skinny extents
Dec 29 15:31:01 localhost kernel: BTRFS info (device sdc2): bdev /dev/sdc2 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0
Dec 29 15:31:01 localhost kernel: BTRFS info (device sdc2): enabling ssd optimizations
Dec 29 15:31:43 localhost kernel: BTRFS warning (device sda3): csum failed root 266 ino 465476 off 36995072 csum 0xdc0d8280 expected csum 0x5ae50870>
Dec 29 15:31:43 localhost kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 23, gen 0
Dec 29 15:31:44 localhost systemd[1]: Started Watch /etc/sysconfig/btrfsmaintenance.
Dec 29 15:31:52 localhost systemd[1]: Started Balance block groups on a btrfs filesystem.
Dec 29 15:31:52 localhost systemd[1]: Started Scrub btrfs filesystem, verify block checksums.
Dec 29 15:31:57 localhost kernel: BTRFS warning (device sda3): csum failed root 266 ino 379878 off 4603904 csum 0x4ca94851 expected csum 0x365f0628 >
Dec 29 15:31:57 localhost kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 24, gen 0
Dec 29 15:32:00 localhost.localdomain kernel: BTRFS warning (device sda3): csum failed root 266 ino 379787 off 32075776 csum 0x0ed9b851 expected csu>
Dec 29 15:32:00 localhost.localdomain kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 25, gen 0
Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:05 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:14 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:20 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:20 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:21 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:21 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
Dec 29 15:32:21 localhost.localdomain kernel: BTRFS error (device sda3): parent transid verify failed on 144883712 wanted 50 found 178
This is my first try with btrfs.
How do I remove the snapshots?
How do I limit them?
btrfs scrub detected checksum errors. List files affected:
**erlangen:~ #** btrfs scrub start -B /
scrub done for e7ad401f-4f60-42ff-a07e-f54372bc1dbc
Scrub started: Fri Jan 1 09:05:26 2021
Status: finished
Duration: 0:00:16
Total to scrub: 33.05GiB
Rate: 1.78GiB/s
Error summary: no errors found
**erlangen:~ #**
Show available space by running:
**erlangen:~ #** btrfs filesystem usage -T /
Overall:
Device size: 51.69GiB
Device allocated: 33.05GiB
Device unallocated: 18.64GiB
Device missing: 0.00B
Used: 28.43GiB
Free (estimated): 22.55GiB (min: 22.55GiB)
Data ratio: 1.00
Metadata ratio: 1.00
Global reserve: 94.50MiB (used: 0.00B)
Multiple profiles: no
Data Metadata System
Id Path single single single Unallocated
-- -------------- -------- -------- -------- -----------
1 /dev/nvme0n1p3 30.01GiB 3.01GiB 32.00MiB 18.64GiB
-- -------------- -------- -------- -------- -----------
Total 30.01GiB 3.01GiB 32.00MiB 18.64GiB
Used 26.10GiB 2.33GiB 16.00KiB
**erlangen:~ #**
‘snapper list’ will display snapshots:
**erlangen:~ #** snapper list
# | Type | Pre # | Date | User | Cleanup | Description | Userdata
-----+--------+-------+--------------------------+------+---------+-----------------------+--------------
0 | single | | | root | | current |
1* | single | | Sun May 17 12:35:27 2020 | root | | first root filesystem |
428 | pre | | Mon Dec 7 12:58:48 2020 | root | number | zypp(zypper) | important=no
429 | post | 428 | Mon Dec 7 12:59:07 2020 | root | number | | important=no
430 | pre | | Wed Dec 9 15:29:07 2020 | root | number | zypp(zypper) | important=no
431 | post | 430 | Wed Dec 9 15:32:02 2020 | root | number | | important=no
432 | pre | | Sat Dec 12 04:59:40 2020 | root | number | zypp(zypper) | important=no
433 | post | 432 | Sat Dec 12 05:06:11 2020 | root | number | | important=no
434 | pre | | Sat Dec 12 07:41:24 2020 | root | number | zypp(zypper) | important=no
435 | post | 434 | Sat Dec 12 07:41:41 2020 | root | number | | important=no
440 | pre | | Sun Dec 13 06:35:30 2020 | root | number | zypp(zypper) | important=no
441 | post | 440 | Sun Dec 13 06:35:52 2020 | root | number | | important=no
442 | pre | | Mon Dec 14 04:08:15 2020 | root | number | zypp(zypper) | important=yes
443 | post | 442 | Mon Dec 14 04:12:00 2020 | root | number | | important=yes
444 | pre | | Mon Dec 14 10:07:27 2020 | root | number | zypp(zypper) | important=no
445 | post | 444 | Mon Dec 14 10:07:40 2020 | root | number | | important=no
446 | pre | | Mon Dec 14 19:44:46 2020 | root | number | zypp(zypper) | important=yes
447 | post | 446 | Mon Dec 14 19:47:12 2020 | root | number | | important=yes
448 | pre | | Mon Dec 14 19:47:51 2020 | root | number | zypp(zypper) | important=yes
449 | post | 448 | Mon Dec 14 19:48:24 2020 | root | number | | important=yes
450 | pre | | Tue Dec 15 17:45:48 2020 | root | number | zypp(zypper) | important=no
451 | post | 450 | Tue Dec 15 17:45:58 2020 | root | number | | important=no
452 | pre | | Tue Dec 15 17:46:21 2020 | root | number | yast bootloader |
453 | post | 452 | Tue Dec 15 17:47:23 2020 | root | number | |
454 | pre | | Thu Dec 17 06:51:50 2020 | root | number | zypp(zypper) | important=yes
455 | post | 454 | Thu Dec 17 06:56:42 2020 | root | number | | important=yes
456 | pre | | Thu Dec 17 08:18:47 2020 | root | number | yast bootloader |
457 | post | 456 | Thu Dec 17 08:19:52 2020 | root | number | |
458 | pre | | Fri Dec 18 19:45:04 2020 | root | number | zypp(zypper) | important=yes
459 | post | 458 | Fri Dec 18 19:46:58 2020 | root | number | | important=yes
460 | pre | | Tue Dec 22 13:40:36 2020 | root | number | zypp(zypper) | important=no
461 | post | 460 | Tue Dec 22 13:47:19 2020 | root | number | | important=no
462 | pre | | Wed Dec 23 02:24:17 2020 | root | number | zypp(zypper) | important=yes
463 | post | 462 | Wed Dec 23 02:26:01 2020 | root | number | | important=yes
468 | pre | | Thu Dec 24 14:22:29 2020 | root | number | zypp(zypper) | important=no
469 | post | 468 | Thu Dec 24 14:22:52 2020 | root | number | | important=no
472 | pre | | Fri Dec 25 09:01:42 2020 | root | number | zypp(zypper) | important=yes
473 | post | 472 | Fri Dec 25 09:10:49 2020 | root | number | | important=yes
474 | pre | | Fri Dec 25 09:16:36 2020 | root | number | zypp(zypper) | important=yes
475 | post | 474 | Fri Dec 25 09:17:07 2020 | root | number | | important=yes
476 | pre | | Sat Dec 26 00:02:26 2020 | root | number | zypp(zypper) | important=no
477 | post | 476 | Sat Dec 26 00:04:07 2020 | root | number | | important=no
478 | pre | | Sat Dec 26 09:34:57 2020 | root | number | zypp(zypper) | important=no
479 | post | 478 | Sat Dec 26 09:35:15 2020 | root | number | | important=no
480 | pre | | Sun Dec 27 16:26:26 2020 | root | number | zypp(zypper) | important=no
481 | post | 480 | Sun Dec 27 16:26:48 2020 | root | number | | important=no
482 | pre | | Sun Dec 27 20:34:39 2020 | root | number | zypp(zypper) | important=no
483 | post | 482 | Sun Dec 27 20:34:50 2020 | root | number | | important=no
484 | pre | | Tue Dec 29 00:05:54 2020 | root | number | zypp(zypper) | important=no
485 | post | 484 | Tue Dec 29 00:06:45 2020 | root | number | | important=no
486 | pre | | Tue Dec 29 08:48:26 2020 | root | number | zypp(zypper) | important=no
487 | post | 486 | Tue Dec 29 08:48:40 2020 | root | number | | important=no
**erlangen:~ #**
With a working installation snapshots will be removed automatically.
couldn’t open file?
btrfs scrub start -B /
WARNING: failed to open status file: Input/output error
WARNING: failed to open the progress status socket at /var/lib/btrfs/scrub.progress.14c5d68e-7778-48e8-adb7-4c164d95181b: Read-only file system. Progress cannot be queried
WARNING: failed to write the progress status file: Read-only file system. Status recording disabled
ERROR: scrubbing / failed for device id 1: ret=-1, errno=30 (Read-only file system)
scrub canceled for 14c5d68e-7778-48e8-adb7-4c164d95181b
Scrub started: Fri Jan 1 12:38:36 2021
Status: aborted
Duration: 0:00:00
Total to scrub: 23.07GiB
Rate: 0.00B/s
Error summary: no errors found
open space
btrfs filesystem usage -T /
Overall:
Device size: 40.03GiB
Device allocated: 23.07GiB
Device unallocated: 16.96GiB
Device missing: 0.00B
Used: 19.13GiB
Free (estimated): 20.32GiB (min: 11.84GiB)
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 35.94MiB (used: 0.00B)
Multiple profiles: no
Data Metadata System
Id Path single DUP DUP Unallocated
-- --------- -------- --------- -------- -----------
1 /dev/sda3 21.01GiB 2.00GiB 64.00MiB 16.96GiB
-- --------- -------- --------- -------- -----------
Total 21.01GiB 1.00GiB 32.00MiB 16.96GiB
Used 17.65GiB 760.72MiB 16.00KiB
snapper list
snapper list
# | Type | Pre # | Date | User | Cleanup | Description | Userdata
-----+--------+-------+---------------------------------+------+---------+-----------------------+--------------
0 | single | | | root | | current |
1* | single | | Wed 28 Oct 2020 10:59:54 PM CDT | root | | first root filesystem |
71 | pre | | Fri 20 Nov 2020 02:57:33 PM CST | root | number | zypp(ruby.ruby2.7) | important=yes
82 | post | 71 | Fri 20 Nov 2020 03:04:32 PM CST | root | number | | important=yes
100 | pre | | Wed 02 Dec 2020 10:32:35 PM CST | root | number | zypp(zypper) | important=yes
101 | pre | | Wed 02 Dec 2020 10:53:36 PM CST | root | number | zypp(zypper) | important=yes
102 | post | 101 | Wed 02 Dec 2020 11:27:38 PM CST | root | number | | important=yes
103 | pre | | Thu 03 Dec 2020 12:59:58 AM CST | root | number | zypp(zypper) | important=yes
104 | post | 103 | Thu 03 Dec 2020 01:01:33 AM CST | root | number | | important=yes
105 | pre | | Thu 24 Dec 2020 12:34:29 PM CST | root | number | yast printer |
106 | post | 105 | Thu 24 Dec 2020 12:37:28 PM CST | root | number | |
107 | pre | | Sat 26 Dec 2020 11:23:19 PM CST | root | number | zypp(zypper) | important=yes
108 | pre | | Sun 27 Dec 2020 09:13:57 AM CST | root | number | zypp(zypper) | important=yes
109 | pre | | Sun 27 Dec 2020 10:29:36 PM CST | root | number | zypp(zypper) | important=yes
110 | pre | | Sun 27 Dec 2020 11:24:29 PM CST | root | number | yast sw_single |
111 | pre | | Sun 27 Dec 2020 11:27:55 PM CST | root | number | zypp(ruby.ruby2.7) | important=no
Thank you and Happy New Year
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 149.1G 0 disk
├─sda1 8:1 0 106G 0 part /windows-C
├─sda2 8:2 0 3G 0 part [SWAP]
└─sda3 8:3 0 40G 0 part /root
sdb 8:16 0 111.8G 0 disk
├─sdb1 8:17 0 23.5G 0 part /home
├─sdb2 8:18 0 84.3G 0 part /backups
└─sdb3 8:19 0 4G 0 part [SWAP]
sdc 8:32 0 232.9G 0 disk
├─sdc1 8:33 0 212.9G 0 part /windows-D
└─sdc2 8:34 0 20G 0 part /linux-back9-LXQT/opt
sr0 11:0 1 1024M 0 rom
Your filesystem is corrupted. You may try to post to btrfs mailing list where developers can request low level dump of metadata and may offer manual steps to recover, but “transid verify failed” almost always means at least some data loss and usually is not repairable.
Nothing you can find on Internet (and nothing written that in this thread) is going to help in this case. Every such failure is unique and you need to know internals to attempt fix. And the only place you will get attention of people who understand internals is btrfs mailing list (or probably IRC).
Or simply preserve data you need and recreate filesystem. It is faster and easier option.
Trouble persists. You may try to diagnose:
**3400G:~ #** btrfsck --force /dev/sda3
Opening filesystem to check...
WARNING: filesystem mounted, continuing because of --force
Checking filesystem on /dev/sda3
UUID: 2b54b9ff-84c9-4db2-841b-aff657a64325
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space cache
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 17564221440 bytes used, no error found
total csum bytes: 14762220
total tree bytes: 744603648
total fs tree bytes: 695484416
total extent tree bytes: 28393472
btree space waste bytes: 166464158
file data blocks allocated: 50144874496
referenced 40237199360
**3400G:~ #**
I realy wonder why you try to do all sorts of things that require writing to that file system in one sort or another. The file system is mounted read-only. You can nothing change/repair here as long as it is.
btrfs check works with unmounted filesystem. But blindly advising doing check with force option is the worst advice someone can give for btrfs.
Sorry, the same for fsck of course.
In any case to me it looks that finding out why it is mounted read only is more important then poking on it from outside.
And I am with you with your advice to copy all, that isn’t already covered by a backup, to a secure place before making it worse.