From: "Vladimir V. Saveliev" <vs@namesys.com>
To: el jeskynar <jeskynar@hotmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: bad blocks on disk. Which files are damaged?
Date: Wed, 05 Apr 2006 19:20:38 +0400 [thread overview]
Message-ID: <1144250438.8444.135.camel@tribesman.namesys.com> (raw)
In-Reply-To: <BAY24-F14A8F21FB4DCCAFF18E792DCCB0@phx.gbl>
Hello
On Wed, 2006-04-05 at 15:12 +0000, el jeskynar wrote:
> Hello,
>
> I never did see an answer to the original poster's question:
>
> "I'd really like to find out which files on the Reiser3.6 FS on the
> defective
> disk are probably damaged."
>
> The bad-block-handling document doesn't seem to cover this,
> how can one find out the names of files containing bad blocks?
>
I guess that such files will get listed by the below command:
find -type f -exec cat {} > /dev/null \;
> I've seen mention of icheck and ncheck tools but 1) I can't find
> them, and 2) I presume they would not work with reiserfs unless
> specifically written so.
>
> Thank you!
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
next prev parent reply other threads:[~2006-04-05 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 15:12 bad blocks on disk. Which files are damaged? el jeskynar
2006-04-05 15:20 ` Vladimir V. Saveliev [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-14 17:25 Fionn Behrens
2005-08-15 9:30 ` Vladimir V. Saveliev
2005-08-15 10:27 ` Sander
2005-08-15 11:07 ` Fionn Behrens
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=1144250438.8444.135.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=jeskynar@hotmail.com \
--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.