linux-ext4 - maintain badblocks list on the fly

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <52C92DC9.7030806@rempel-privat.de>
Date:	Sun, 05 Jan 2014 11:02:49 +0100
From:	Oleksij Rempel <linux@...pel-privat.de>
To:	linux-ext4@...r.kernel.org
Subject: maintain badblocks list on the fly

Hello all,

after some googling i didn't found answer to my question, so i set it
directly here: do it makes sense and is it possible to maintain bad
block list of ext4 on fly? I mean, if ext4 get error from, for example
from ata subsystem, and it will mark block as bad or may be better as
"probably bad"?

Since ext4 do anyway journal recovery, it can do some sort of
auto-repair too.

The reason why i ask is a story of laptop which i got for repair. After
update, system failed to boot. One of system relevant files was placed
on badblock which was already detected by kernel one month(!) before (it
can be found in syslog). After reboot, system was unusable for average
user. It is single bad block for 500GB, so it is not the case for
replacement.

In case if ext4 would maintain bad blocks on the fly, it would keep the
system working. Hi-level tools should be responsible to notify user
about FS and device degradation.

PS: thanks for metadata_csum :)
-- 
Regards,
Oleksij

Download attachment "signature.asc" of type "application/pgp-signature" (296 bytes)