I am getting errors while launching any container or downloading new apps with the error no space left. I tried to run the balance command to get this output:

 

root@MewTwo:~# btrfs balance start -dusage=5 /mnt/cache
ERROR: error during balancing '/mnt/cache': Read-only file system
There may be more info in syslog - try dmesg | tail

 

On running dmesg | tail, 

 

root@MewTwo:~# dmesg | tail
[  894.653227] loop: Write error at byte offset 17481728, length 4096.
[  894.653229] blk_print_req_error: 73 callbacks suppressed
[  894.653230] I/O error, dev loop2, sector 2202048 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
[  894.653233] I/O error, dev loop2, sector 34144 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2
[  894.653235] btrfs_dev_stat_inc_and_print: 73 callbacks suppressed
[  894.653236] BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 85, rd 0, flush 0, corrupt 1, gen 0
[  894.653242] I/O error, dev loop2, sector 2272904 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2
[  894.653243] BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 86, rd 0, flush 0, corrupt 1, gen 0
[ 2181.508753] elogind-daemon[1305]: Removed session c1.
[ 2494.920558] elogind-daemon[1305]: New session c2 of user root.

 

The logs suggest something is wrong with disk5, but SMART is all OK. However, the disk shows only 180KB free while all my shares have "High Water" enabled. 

 

Edit:
I am not able to do anything with docker now and log shows this error:
 

Aug 29 14:09:08 MewTwo kernel: BTRFS error (device nvme0n1p1: state EA): parent transid verify failed on logical 846885584896 mirror 1 wanted 2286467 found 2286420
Aug 29 14:09:08 MewTwo kernel: BTRFS error (device nvme0n1p1: state EA): parent transid verify failed on logical 846885584896 mirror 1 wanted 2286467 found 2286420

 

I referred to the issue here: 

 

mewtwo-diagnostics-20240829-0949.zip

Edited August 29, 20241 yr by geekmay

Pool is going read-only, with btrfs recommend backing it up and then re-formatting, also a good idea to run memtest since data corruption was being detected.