ext4 file system corruption - again

From	Jesper Dybdal <jd-debian-user@dybdal.dk>
Newsgroups	linux.debian.user
Subject	ext4 file system corruption - again
Date	2024-09-23 11:30 +0200
Message-ID	<JpNyh-efLc-3@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

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 name as the old one had). That file was 
/etc/postfix/master.cf - a simple text configuration file that is 
modified only manually using emacs.

I wrote about it here when it first happened - that thread began with:
    Message-ID: <bf46ee0b-8af1-43ce-a48f-e304ef850b3d@dybdal.dk>
    Date: Tue, 19 Mar 2024 15:43:30 +0100
    Subject: Filsystemkorruption i ext4?

I don't believe that it is a disk error - the file system is on a RAID1 
partition and the RAID consistency is checked regularly.
I also find it hard to believe that it is a RAM error - the mashine has 
run memtest86+ overnight without finding anything.
There was a power outage some time ago, but surely ext4 should be able 
to handle that without introducing errors.

Fsck fixes it.
The system is an up-to-date Bookworm.

Any ideas as to how this can happen - twice, and effecting (among 
others) the same file?

---------------- 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. FIXED.
root: Inode 10751288, i_blocks is 281474976710647, should be 3. FIXED.
root: 223986/32759808 files (6.5% non-contiguous), 6827061/131038976 blocks
fsck exited with status code 1

---------------- stat(1) for the two files before fsck:
   File: main.cf
   Size: 16959         Blocks: 2251799813685048 IO Block: 4096 regular file
Device: 9,0    Inode: 10748715    Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/ root)
Access: 2024-09-22 20:31:58.081768853 +0200
Modify: 2024-08-03 19:33:20.665350446 +0200
Change: 2024-09-22 22:09:54.053359071 +0200
  Birth: 2024-08-03 11:20:14.671832520 +0200

   File: master.cf
   Size: 10782         Blocks: 2251799813685176 IO Block: 4096 regular file
Device: 9,0    Inode: 10751288    Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/ root)
Access: 2024-09-22 19:20:07.216191493 +0200
Modify: 2024-06-05 14:37:24.205001097 +0200
Change: 2024-09-22 22:09:54.053359071 +0200
  Birth: 2024-03-19 13:36:38.971618859 +0100
----------------

Thanks,
Jesper

-- 
Jesper Dybdal
https://www.dybdal.dk

Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

ext4 file system corruption - again Jesper Dybdal <jd-debian-user@dybdal.dk> - 2024-09-23 11:30 +0200
  Re: ext4 file system corruption - again Arno Lehmann <al@its-lehmann.de> - 2024-09-23 12:00 +0200
    Re: ext4 file system corruption - again Jesper Dybdal <jd-debian-user@dybdal.dk> - 2024-09-24 11:10 +0200
  Re: ext4 file system corruption - again Stefan Monnier <monnier@iro.umontreal.ca> - 2024-09-23 16:20 +0200
    Re: ext4 file system corruption - again Jesper Dybdal <jd-debian-user@dybdal.dk> - 2024-09-26 15:30 +0200

csiph-web