You are not logged in.
Pages: 1
I noticed an issue with my btrfs filesystem or harddrive after the filesystem remounted itself as read only. I'm surprised that the second scrub didn't find any errors. So how bad is it? Making a backup now.
Check sum errors in dmesg:
[ 344.966585] BTRFS warning (device dm-0): csum failed root 257 ino 21378 off 7980032000 csum 0x33a7ab75 expected csum 0x00000000 mirror 1
[ 344.966589] BTRFS error (device dm-0): bdev /dev/mapper/verschl errs: wr 0, rd 0, flush 0, corrupt 3, gen 0
[ 363.344209] BTRFS warning (device dm-0): csum failed root 257 ino 21378 off 7980032000 csum 0x33a7ab75 expected csum 0x00000000 mirror 1
[ 363.344211] BTRFS error (device dm-0): bdev /dev/mapper/verschl errs: wr 0, rd 0, flush 0, corrupt 4, gen 0
[ 382.679571] BTRFS warning (device dm-0): csum failed root 257 ino 21378 off 7980032000 csum 0x33a7ab75 expected csum 0x00000000 mirror 1
[ 382.679576] BTRFS error (device dm-0): bdev /dev/mapper/verschl errs: wr 0, rd 0, flush 0, corrupt 5, gen 0
[ 417.898883] BTRFS warning (device dm-0): csum failed root 257 ino 21378 off 7980032000 csum 0x33a7ab75 expected csum 0x00000000 mirror 1
[ 417.898887] BTRFS error (device dm-0): bdev /dev/mapper/verschl errs: wr 0, rd 0, flush 0, corrupt 6, gen 0
[ 440.434523] BTRFS warning (device dm-0): csum failed root 257 ino 21378 off 7980032000 csum 0x33a7ab75 expected csum 0x00000000 mirror 1
[ 440.434526] BTRFS error (device dm-0): bdev /dev/mapper/verschl errs: wr 0, rd 0, flush 0, corrupt 7, gen 0
[ 461.920319] BTRFS warning (device dm-0): csum failed root 257 ino 21378 off 7980032000 csum 0x33a7ab75 expected csum 0x00000000 mirror 1
[ 461.920323] BTRFS error (device dm-0): bdev /dev/mapper/verschl errs: wr 0, rd 0, flush 0, corrupt 8, gen 0
[ 480.269072] BTRFS warning (device dm-0): csum failed root 257 ino 21378 off 7980032000 csum 0x33a7ab75 expected csum 0x00000000 mirror 1
[ 480.269075] BTRFS error (device dm-0): bdev /dev/mapper/verschl errs: wr 0, rd 0, flush 0, corrupt 9, gen 0First scrub output
sudo sudo btrfs scrub status /
UUID: 33dc7187-ac3c-4536-8a3a-b7f8a608dff9
Scrub started: Wed Nov 4 20:13:29 2020
Status: finished
Duration: 0:00:49
Total to scrub: 90.47GiB
Rate: 1.85GiB/s
Error summary: csum=1
Corrected: 0
Uncorrectable: 1
Unverified: 0Second scrub output
sudo sudo btrfs scrub status /
UUID: 33dc7187-ac3c-4536-8a3a-b7f8a608dff9
Scrub started: Wed Nov 4 20:20:52 2020
Status: finished
Duration: 0:00:57
Total to scrub: 89.38GiB
Rate: 1.57GiB/s
Error summary: no errors foundLast edited by teateawhy (2020-11-04 19:27:46)
Offline
Any reason for the double sudo?
Anyways have you done a S.M.A.R.T check recently? Could be bit rot...and that is a warning sign...
Good idea on the backup tho.
What kind of setup is this?
Plain btrfs or you are doing a RAID?
I assume btrfs on LUKS
Last edited by GaKu999 (2020-11-06 10:36:17)
Offline
Double sudo doesn't matter
I have looked at Smart output and it looks ok, but I will see if Samsung has their own tools and check again with that.
This setup is btrfs on LUKS.
I think that this could also be related to RAM over clocking or bad suspend to ram support. I haven't seen any checksum errors since I turned off the RAM overclock, but I also haven't used suspend to disk. I more strongly suspect the suspend to disk issue atm because it gave me a warning before I will try to dig up that warning again.
Question: If in the log output, the line says
corrupt: 9 , does that mean there is 9 bad blocks on the disk? Or that there are additional 9 since the last time?
Offline
I have no idea, could be then a little RAM corruption...
You should give a little memtest run just to be sure, before sleeping setup memtest and let it run the whole night, to rule out RAM shenanigans just in case (with overclocking disabled and later another test with it enabled).
Considering you use LUKS you need to be 100% sure your RAM is ok at this point...(that’s what I think, tho I may be wrong, anyways it’s no good to have bit rot in RAM...)
Last edited by GaKu999 (2020-11-07 02:06:16)
Offline
Pages: 1