From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] e2fsck -c when bad blocks are in existing file?
Date: Tue, 8 Nov 2022 03:31:07 -0000 (UTC) [thread overview]
Message-ID: <tkcihr$vdc$1@ciao.gmane.io> (raw)
I've got an SSD that's failing, and I'd like to know what files
contain bad blocks so that I don't attempt to copy them to the
replacement disk.
According to e2fsck(8):
-c This option causes e2fsck to use badblocks(8) program to do a
read-only scan of the device in order to find any bad blocks. If
any bad blocks are found, they are added to the bad block inode
to prevent them from being allocated to a file or directory. If
this option is specified twice, then the bad block scan will be
done using a non-destructive read-write test.
What happens when the bad block is _already_allocated_ to a file?
--
Grant
next reply other threads:[~2022-11-08 3:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 3:31 Grant Edwards [this message]
2022-11-08 13:20 ` [gentoo-user] e2fsck -c when bad blocks are in existing file? Michael
2022-11-08 14:28 ` [gentoo-user] " Grant Edwards
2022-11-08 17:55 ` Laurence Perkins
2022-11-08 18:49 ` Michael
2022-11-08 21:52 ` John Covici
2022-11-09 23:31 ` Grant Edwards
2022-11-09 23:54 ` Wol
2022-11-10 0:18 ` Grant Edwards
2022-11-10 0:37 ` Laurence Perkins
2022-11-08 18:24 ` [gentoo-user] " Wols Lists
2022-11-09 8:46 ` Michael
2022-11-09 16:53 ` Laurence Perkins
2022-11-12 13:38 ` Michael
2022-11-12 16:44 ` [gentoo-user] " Grant Edwards
2022-11-12 19:34 ` Michael
2022-11-13 3:54 ` Grant Edwards
2022-11-14 16:37 ` Laurence Perkins
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='tkcihr$vdc$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.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