Re: ext4 file system corruption - again

[Jesper Dybdal <jd-debian-user@dybdal.dk>]

    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/131038976 blocks
>       
>       
>       I do not think it is likely to be a hardware problem. The bit
>       patterns for the number of blocks you quote actually have all the
>       high bits of the potentially used 48 bits of the block count set 
    ...
> The
>       large values with peculiar bit patterns do look like some flag
>       values to me. It might be worth asking among the ext4 developers
>       if those values could be introduced by some particular condition,
>       I think.
>       
>     
    
    I think I'll do that.

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, should be 3. FIXED.
> >       
>                                    ^^^^^^^^^^^^^^^
> AKA -9
>
> It's odd that it looks like -N².  Maybe it's just happenstance, but I'd
> be curious to see if you have other "data points".
>     
    Unfortunately, I have no other "data points".  The data from the
    first occurrence of this are lost.
    
    Many thanks to Arno and Stefan - I probably had not noticed the
    interesting values without their help.
    
    Jesper
-- 
Jesper Dybdal
https://www.dybdal.dk