From: Oleksij Rempel <linux@rempel-privat.de>
To: linux-ext4@vger.kernel.org
Subject: maintain badblocks list on the fly
Date: Sun, 05 Jan 2014 11:02:49 +0100 [thread overview]
Message-ID: <52C92DC9.7030806@rempel-privat.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 bytes --]
next reply other threads:[~2014-01-05 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 10:02 Oleksij Rempel [this message]
2014-01-06 1:27 ` maintain badblocks list on the fly Theodore Ts'o
2014-01-16 9:50 ` Oleksij Rempel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52C92DC9.7030806@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox