On 25.01.2020 16:44 Thorsten Hirsch wrote: > Thanks, guys. > > However, checking the RAM with memtest86 hasn't revealed any errors. > Currently I let it run another pass, but so far everything's good. > Here's the output of btrfs check... just from my experience with non-ECC RAM: When I had RAM corruption it only occurred after a few days of uptime and only when I ran memtester on Linux. memtest86/memtest86+ didn't show any problems even when running for a week (and in multi cpu mode). > [1/7] checking root items > [2/7] checking extents > leaf parent key incorrect 109690880 > bad block 109690880 > ERROR: errors found in extent allocation tree or chunk allocation > [3/7] checking free space cache > [4/7] checking fs roots > root 5 inode 3583162 errors 1040, bad file extent, some csum missing > root 5 inode 3767022 errors 1040, bad file extent, some csum missing > root 5 inode 3819591 errors 1040, bad file extent, some csum missing > root 5 inode 4108194 errors 1040, bad file extent, some csum missing > ERROR: errors found in fs roots > Opening filesystem to check... > Checking filesystem on /dev/nvme0n1p3 > UUID: 26717c9f-df62-4c57-a482-b9e4880b31e6 > found 6132469760 bytes used, error(s) found > total csum bytes: 0 > total tree bytes: 4161536 > total fs tree bytes: 0 > total extent tree bytes: 3850240 > btree space waste bytes: 1115823 > file data blocks allocated: 108003328 > referenced 108003328 >
