Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #268392

Filsystemkorruption i ext4?

From Jesper Dybdal <jd-debian-user@dybdal.dk>
Newsgroups linux.debian.user
Subject Filsystemkorruption i ext4?
Date 2024-03-19 15:50 +0100
Message-ID <IjIWS-b9R-27@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


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

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


Thread

Filsystemkorruption i ext4? Jesper Dybdal <jd-debian-user@dybdal.dk> - 2024-03-19 15:50 +0100
  Re: Filsystemkorruption i ext4? Franco Martelli <martellif67@gmail.com> - 2024-03-19 21:50 +0100
    Re: Filsystemkorruption i ext4? Jesper Dybdal <jd-debian-user@dybdal.dk> - 2024-03-20 09:20 +0100
      Re: Filsystemkorruption i ext4? Franco Martelli <martellif67@gmail.com> - 2024-03-20 16:10 +0100
    Re: Filsystemkorruption i ext4? Jesper Dybdal <jd-debian-user@dybdal.dk> - 2024-03-20 14:30 +0100
      Re: Filsystemkorruption i ext4? Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-03-20 23:00 +0100
        Re: Filsystemkorruption i ext4? Jesper Dybdal <jd-debian-user@dybdal.dk> - 2024-03-28 14:40 +0100
        Re: Filsystemkorruption i ext4? Jesper Dybdal <jd-debian-user@dybdal.dk> - 2024-03-28 15:00 +0100
          Re: Filsystemkorruption i ext4? Hans <hans.ullrich@loop.de> - 2024-03-28 15:10 +0100
            Re: Filsystemkorruption i ext4? Jesper Dybdal <jd-debian-user@dybdal.dk> - 2024-03-28 16:10 +0100
              Re: Filsystemkorruption i ext4? Hans <hans.ullrich@loop.de> - 2024-03-28 16:40 +0100

csiph-web