All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fionn Behrens <fionn@spamfilter.de>
To: reiserfs-list@namesys.com
Subject: Re: bad blocks on disk. Which files are damaged?
Date: Mon, 15 Aug 2005 13:07:51 +0200	[thread overview]
Message-ID: <1124104066.25727.10.camel@laptop> (raw)
In-Reply-To: <430060B4.7070906@namesys.com>

[-- Attachment #1: Type: text/plain, Size: 921 bytes --]

On Mo, 2005-08-15 at 13:30 +0400, Vladimir V. Saveliev wrote:

> You might want to look at
> http://namesys.com/bad-block-handling.html
> 
> I believe it is in uptodate state. Yes, Vitaly?

thanks for the link. The page has not been updated recently it seems but
it has some good advice. I must admit, though, that I'd rather like to
find out the defective files first and try to copy all unaffected files
BEFORE I do an fsck. Because I am afraid I could lose pointers to
otherwise unharmed files during a --rebuild-tree.

None of the tools on that page seems to be able to just point out which
files could be damaged from the badblocks list... and that was my
initial problem.

best regards,
		Fionn
-- 
 "We view Intellectual Property theft as a threat
  to our national security," (http://beam.me.to/?iptheft-terrorism)
*** David Israelite, Ashcroft Deputy and Chief of "US DOJ IP Task Force"


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-08-15 11:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 17:25 bad blocks on disk. Which files are damaged? Fionn Behrens
2005-08-15  9:30 ` Vladimir V. Saveliev
2005-08-15 10:27   ` Sander
2005-08-15 11:07   ` Fionn Behrens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-05 15:12 el jeskynar
2006-04-05 15:20 ` Vladimir V. Saveliev

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=1124104066.25727.10.camel@laptop \
    --to=fionn@spamfilter.de \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.