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

Groups > linux.debian.user > #268581

Re: Filsystemkorruption i ext4?

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 2024-03-28 15:02, Hans wrote:
> Am Donnerstag, 28. März 2024, 14:49:37 CET schrieb Jesper Dybdal:
> Hello,
>
> memtest86+ is for testing RAM, but do you not want to test ext4 filesystem?

Sorry - I should have left more of the previous mails quoted.  I have 
previously tested the RAID1 consistency (ok), fixed the file system 
(found 3 files with incorrect block count), and now also tested the 
RAM.And since it seems unlikely that it is a bug in ext4 (in Debian 
Bullseye), I don't quite understand how such an inconsistency can occur. 
Thanks for your response, Jesper
> If so, I suggest to boot a live system like Knoppix or similar, then run your
> test by using
>
> e2fsck -y /dev/sda1
>
> or wherever your filesystem resides.
>
> Please pay attention: If you have encrypted filesystems, then first open the
> encryption, do NOT mount the filesystem and then check it, for example:
>
> cryptsetup luksOpen /dev/sda1 data1
>
> then enter the password and now you can run
>
> e2fsck -y /dev/mapper/data1
>
> Note: the word "data1" is only an example, you can name it, whatever you want
> like "space", "soap", "bullet", "henry" or whatever.
>
> Hope this helps.
>
> Best
>
> Hans
>
>
>
>> [Sorry - I accidentally sent this too quickly in an incomplete state.
>> Second try here:]
>>
>>> On Wed, Mar 20, 2024, 11:28 AM Jesper Dybdal
>>>
>>> <jd-debian-user@dybdal.dk>  wrote:
>>>      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've now let memtest86+ run for 9 hours, during which it did 14 passes
>> of all its tests.  It found nothing wrong.
>>
>> On 2024-03-20 22:58, Nicholas Geovanis wrote:
>>> 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.
>> There is only one RAM stick (of 16 GB), so there should be no problems
>> of that kind.
>>
>> I'm afraid I won't find an explanation of that file system corruption :-(
>>
>> Thanks to Franco and Nicholas for your responses,
>> Jesper
>
>
>

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

Back to linux.debian.user | Previous | Next — Previous in thread | 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