Re: ext4 file system corruption - again

2024-09-26 Thread Jesper Dybdal
On 2024-09-23 16:10, Stefan Monnier wrote: root has been mounted 13 times without being checked, check forced. root: Inode 10748715, i_blocks is 281474976710631, should be 5. FIXED. ^^^ AKA -25 root: Inode 10751288, i_blocks is 281474976710647,

Re: ext4 file system corruption - again

2024-09-24 Thread Jesper Dybdal
On 2024-09-23 11:55, Arno Lehmann wrote: Am 23.09.2024 um 11:20 schrieb Jesper Dybdal: ... > root: Inode 10748715, i_blocks is 281474976710631, should be 5. FIXED. > root: Inode 10751288, i_blocks is 281474976710647, should be 3. FIXED. > root: 223986/32759808 files (6.5% non-contiguous), 6827061

Re: ext4 file system corruption - again

2024-09-23 Thread Stefan Monnier
> root has been mounted 13 times without being checked, check forced. > root: Inode 10748715, i_blocks is 281474976710631, should be 5. FIXED. ^^^ AKA -25 > root: Inode 10751288, i_blocks is 281474976710647, should be 3. FIXED.

Re: ext4 file system corruption - again

2024-09-23 Thread Arno Lehmann
Hi Jesper, Am 23.09.2024 um 11:20 schrieb Jesper Dybdal: ... > fsck log: > Log of fsck -C -a -T -t ext4 /dev/md0 > Sun Sep 22 20:20:13 2024 > > root has been mounted 13 times without being checked, check forced. > root: Inode 10748715, i_blocks is 281474976710631, should be 5. FI

ext4 file system corruption - again

2024-09-23 Thread Jesper Dybdal
Some time ago I had a problem with the i_blocks field of a few inodes being corrupted (replaced by extremely large numbers). It now happened again, and the strange thing is that one of the two files affected was also affected the earlier time (or more precisely, the file that now has the same