Re: ext4 file system corruption - again

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

    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".
>
>     
    One more "data point" just appeared today.  I had edited /etc/fstab
    and rebooted, and then fstab suddenly had the problem.:
    
    root: Inode 10748542, i_blocks is 281474976710653, should be 1. 
    FIXED.
    AKA -3, so not of the  -N²
    form.
    
    From a stat() (after the fsck that repaired the file):
      File: fstab
      Size: 1855          Blocks: 8          IO Block: 4096   regular
    file
    
    I haven't yet had time to describe the problem on the ext4 mailing
    list.  I have remembered that there is one thing I do differently
    from the default: I use the ext4 option "nodelalloc" (because
    several years ago, there was a discussion about "delalloc or not"
    from which It seemed that nodelalloc was probably slightly safer -
    if the associated performance reduction is not a problem, which it
    is not for me).
    
    I've now turned nodelalloc off, just in case that changes something.
-- 
Jesper Dybdal
https://www.dybdal.dk