From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Fionn Behrens <fionn@spamfilter.de>
Cc: reiserfs-list@namesys.com, Vitaly Fertman <vitaly@namesys.com>
Subject: Re: bad blocks on disk. Which files are damaged?
Date: Mon, 15 Aug 2005 13:30:28 +0400 [thread overview]
Message-ID: <430060B4.7070906@namesys.com> (raw)
In-Reply-To: <1124040310.14141.4.camel@laptop>
Hello
Fionn Behrens wrote:
> Hello all...
>
> I have a harddisk here which developed bad blocks. It is quite large and
> only a few blocks seem to be affected. I ran several scans wirh the
> "badblocks" tool and got a map of defective blocks out of this. Now I'd
> really like to find out which files on the Reiser3.6 FS on the defective
> disk are probably damaged.
> Is there a way or maybe even a HowTo to tell this without huge effort?
You might want to look at
http://namesys.com/bad-block-handling.html
I believe it is in uptodate state. Yes, Vitaly?
> Maybe even some kind of script or tool?
>
> best regards,
> Fionn
next prev parent reply other threads:[~2005-08-15 9:30 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 [this message]
2005-08-15 10:27 ` Sander
2005-08-15 11:07 ` Fionn Behrens
-- 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=430060B4.7070906@namesys.com \
--to=vs@namesys.com \
--cc=fionn@spamfilter.de \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.