Hi Jesper,
Am 23.09.2024 um 11:20 schrieb Jesper Dybdal:
...
> ---------------- 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
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, for example
111111111111111111111111111111111111111111100111 and given that the 16
higher bits are not stored next to the lower 32 bits, there should be
many other values and flags set to all ones, which should result in
other things to notice -- for example, the file should be considered to
be part of the file system structure and compressed, which fsck should
loudly complain about (not verified).
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.
Cheers,
Arno
--
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
