I have now done the following:
* Checked the RAID array - no problems found.
* Run fsck. It found three cases of the block count being incorrect. I
don't know which the other two affected files are.
* Run one pass of memtest86+. Nothing found.
So it seems not to be a problem with the disks.
A bug in ext4? Well, ext4 has always done its job for me wihtout problems.
A RAM error that memtest86+ did not find? Possible. Once upon a time,
when you bought an ordinary pc, its RAM had ECC as a matter of course;
unfortunately, that is not the case nowadays.
I think I'll let memtest86+ run overnight one of the coming nights.
Unless it is simply a RAM error, then it is a bit scary...
I have seen that a couple times, unlikely but possible. Maybe review your RAM configuration too, ensure that the sticks are on the same supported refresh rate and distributed across the slots in an approved way.
Regards,
Jesper
On 2024-03-19 21:47, Franco Martelli wrote:
> On 19/03/24 at 15:43, Jesper Dybdal wrote:
>
>>
>> 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.
>
> Another check you can perform it is on the RAID array, by default it
> runs on the first Sunday of each month at 00:57. You should have this
> file /etc/cron.d/mdadm that takes care to run this check monthly.
>
> Before you reboot, does it look OK /proc/mdstat ?
>
--
Jesper Dybdal
https://www.dybdal.dk