linux-ext4 - [Bug 201685] ext4 file system corruption

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 25 Nov 2018 07:59:32 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 201685] ext4 file system corruption

https://bugzilla.kernel.org/show_bug.cgi?id=201685

HB (hb@...twelt.deneb.uberspace.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hb@...twelt.deneb.uberspace
                   |                            |.de

--- Comment #41 from HB (hb@...twelt.deneb.uberspace.de) ---
I have this bug with ubuntu 18.04 kernel 4.15.0-39, too.

My Desktop: 
SSD (Samsung 840) with three partions:
/boot : ext2
/     : ext4
swap

HDD1: one ext4 partition
HDD2: luks encrypted, never mounted at boot time and not used when the error
happens.

No Raid-Stuff used.

The problems only occurs on the ext4 part. from the ssd.

Sometimes at booting there are some message like "could not access ata
devices", there are some timeouts with ATA-commands. It retries several times
until it gives up, I dont reach the busy box command line.

Sometimes I reach the busybox command line but cant fix it there, because there
is no fsck in busybox.

I have to connect the ssh to a notebook via usb2sata Adapter, the two partions
were recognised without problems and are in most cases automounted. If I force
a fsck there are some orphaned inodes discovered and the fs is fixed.

After this I can boot from this SSD in the desktop without problems until it
happens again.

The weired thing is that sometimes the SSD is not recognised after this and has
this ATA-Timeouts above.

Even turning the desktop completeley powerless (disconnecting from power socket
and waiting some minutes then doing a cold boot) it gets stuck the same way.

On the notbook were I fix the SSD is the same OS installed and there never
occured this type of problem. Maybe I had only luck until now, I dont use the
notebook very much.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.