I have just discovered that my Debian Bullseye server thinks that a file
has allocated 2251799813684984 blocks (!):
root@nuser:/etc/postfix# stat master.cf.bad-size
File: master.cf.bad-size
Size: 10782 Blocks: 2251799813684984 IO Block: 4096 regular
file
Device: 900h/2304d Inode: 10748971 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2024-03-19 15:23:01.002627532 +0100
Modify: 2024-03-11 16:16:22.152186851 +0100
Change: 2024-03-19 13:37:44.647279278 +0100
Birth: 2023-06-13 01:07:54.542855184 +0200
The file can be read and has the correct contents. (I've renamed it and
replaced master.cf by a fresh backup copy, so nothing will be missed if
fsck deletes the bad file.)
It seems to me that there is a file system corruption and/or a disk
error and/or a RAM error.
Had anyone else seen something like this?
(I haven't rebooted or run fsck yet, because I want to put a monitor on
the machine first and have time to solve problemr - and I haven't got
that time right now.)
My plan is to boot a rescue disk and mount that partition read-only. Then:
* If the file looks ok after reboot, then I'll strongly suspect the RAM
- and run memtest.
* Otherwise, I'll have to run fsck and see what happens.
kernel version:
root@nuser:~# uname -a
Linux nuser 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64
GNU/Linux
The partition in question is a RAID 1 controlled by md.
Thanks,
Jesper
--
Jesper Dybdal
https://www.dybdal.dk
