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


Groups > linux.debian.user > #261661

Re: using ddrescue on the root partition - boot with / as read-only

From Michael Kjörling <2695bd53d63c@ewoof.net>
Newsgroups linux.debian.user
Subject Re: using ddrescue on the root partition - boot with / as read-only
Date 2023-09-14 14:50 +0200
Message-ID <HdTXb-8VQz-1@gated-at.bofh.it> (permalink)
References <HdwQV-8I0j-1@gated-at.bofh.it> <HdLGh-8QLo-1@gated-at.bofh.it> <HdRC1-8Uwl-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 14 Sep 2023 12:17 +0200, from vincent@vinc17.net (Vincent Lefevre):
> badblocks says that there are 25252 bad blocks.
> 
> I'm using ddrescue before doing anything else (mainly in case things
> would go worse), but I would essentially be interested in knowing
> which files are affected.

There's always the brute-force way; for each ordinary file, try to cat
it to /dev/null, and log the name of the file if that fails.

Alternatively, since you have an on-disk offset, you might be able to
use `debugfs -R "stat <filename>"` or `hdparm --fibmap <filename>` or
`filefrag -e <filename>` for each file visible to figure out which
file name(s) map to that location on disk.

I couldn't immediately find a convenient way to go from an on-disk
offset to a file name directly.

-- 
Michael Kjörling                     🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-13 14:10 +0200
  Re: using ddrescue on the root partition - boot with / as read-only <tomas@tuxteam.de> - 2023-09-13 14:20 +0200
    Re: using ddrescue on the root partition - boot with / as read-only tomas@tuxteam.de - 2023-09-13 14:30 +0200
    Re: using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-13 16:00 +0200
      Re: using ddrescue on the root partition - boot with / as read-only Stefan Monnier <monnier@iro.umontreal.ca> - 2023-09-14 05:10 +0200
        Re: using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-14 11:30 +0200
          Re: using ddrescue on the root partition - boot with / as read-only Stefan Monnier <monnier@iro.umontreal.ca> - 2023-09-14 18:10 +0200
  Re: using ddrescue on the root partition - boot with / as read-only David Christensen <dpchrist@holgerdanske.com> - 2023-09-14 06:00 +0200
    Re: using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-14 12:20 +0200
      Re: using ddrescue on the root partition - boot with / as read-only Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-09-14 14:50 +0200
        Re: using ddrescue on the root partition - boot with / as read-only Max Nikulin <manikulin@gmail.com> - 2023-09-14 16:50 +0200
          Re: using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-14 17:40 +0200
      Re: using ddrescue on the root partition - boot with / as read-only David Christensen <dpchrist@holgerdanske.com> - 2023-09-15 07:30 +0200
        Re: using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-15 14:50 +0200
          Re: using ddrescue on the root partition - boot with / as read-only David Christensen <dpchrist@holgerdanske.com> - 2023-09-15 23:00 +0200

csiph-web