From: Ragnar Hojland Espinosa <ragnar@linalco.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: problem with a bad block in bitmap table
Date: Wed, 27 Aug 2003 17:10:20 +0200 [thread overview]
Message-ID: <20030827151020.GA14852@linalco.com> (raw)
In-Reply-To: <200308271828.45686.vitaly@namesys.com>
On Wed, Aug 27, 2003 at 06:28:45PM +0400, Vitaly Fertman wrote:
> this is unfortunatelly the block the reiserfs keeps its system info in,
> and there is no way to relocate it or just mark as bad.
Ugh. May I suggest the obvious, adding this into reiserfss new versions..
> Have you tried to write into this block? If the internal harddrive's list of badblocks
> is not full, it may get remapped and block may become readable again. In the
I tried, didn't do anything. I'm also getting a few AddrMarkNotFound
errors, so its quite well headed onto the dead pile.
> case this succeeds you will need to run reiserfsck --fix-fixable after. But if it
> does not, that means that you have a lot of bad blocks and there is no space
> in the harddrive internal list of bad blocks -- you really need to replace the
> harddrive. While replacing you can run
> dd if=/dev/hdb2 of=somewhere conv=sync,noerror
> (or even better to use dd_rescue).
> Am I right that hdb2 is the fauly one?
Yeah. I attempted to dd if=/dev/hdb2 conv=sync,noerror |gzip to see
if i could make it fit somewhere and still have a backup, but even if
the HD has 50 GB free it doesn't compress well.. I could had tried to
clean the unused blocks with 0s, but it doesn't look too
straightforward with that bitmap in the middle.. so I'm gonna take it
to work, backup it there, pray, and try your --fix-fixable suggestion.
> the tree inself is ok (I hope), but reiserfs has some system info in the block
> that is not readable anymore. If you really want to continue with this broken
> harddrive and need our assistance, visit please our support page
> (www.namesys.com/support.html) -- we deal with hardware problems in term
> of this page.
I actually would love to get rid of it ;) Thanks.
--
Ragnar Hojland - Project Manager
Linalco "Specialists in Linux and Free Software"
http://www.linalco.com Tel: +34-91-5970074 Fax: +34-91-5970083
prev parent reply other threads:[~2003-08-27 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 13:20 problem with a bad block in bitmap table Ragnar Hojland Espinosa
2003-08-27 14:28 ` Vitaly Fertman
2003-08-27 15:10 ` Ragnar Hojland Espinosa [this message]
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=20030827151020.GA14852@linalco.com \
--to=ragnar@linalco.com \
--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.