From: Dirk Leber <dirk.leber@web.de>
To: reiserfs-list@namesys.com
Subject: How to work around bad blocks?
Date: Mon, 10 Mar 2003 21:15:50 -0800 [thread overview]
Message-ID: <200303102115.50039.dirk.leber@web.de> (raw)
Hello List,
I am the unhappy owner of a "corrupt" ReiserFS. All the other partitions on
the same disk work fine, just this one seems to have some bad blocks. HEre
are some outputs:
> mount /dev/hda4 /mnt/data2/
mount: wrong fs type, bad option, bad superblock on /dev/hda4,
or too many mounted file systems
> reiserfsck --check
[no problem]
> reiserfsck --fix-fixable /dev/hda4
reiserfsck 3.6.2 (2002)
Will check consistency of the filesystem on /dev/hda4
Will fix what can be fixed w/o --rebuild-tree
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes):Yes
###########
reiserfsck --fix-fixable started at Mon Mar 10 20:50:03 2003
###########
bread: Cannot read a block # 7503872.
> badblocks -b 4096
[detects bad blocks 7503858 - 7503871]
Obviously the build-tree option also fails. The "How Reiser handles Bad
blocks-FAQ" can only be considered a bad joke, since you need a degree in
computer science AND a mountable filesystem for fooling the FS in that way.
What I would like to do is, detecting the bad blocks, freeing them (accepting
there content) rebuilding the tree (or not) and than mounting it while
accepting that some files will be corrupt.
What can I do?
Dirk
next reply other threads:[~2003-03-11 5:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 5:15 Dirk Leber [this message]
2003-03-10 20:50 ` How to work around bad blocks? Anders Widman
2003-05-08 11:18 ` power loss -> corruption Mirar
2003-05-08 11:48 ` Dieter Nützel
2003-05-08 12:06 ` Mirar
2003-05-08 13:02 ` Dieter Nützel
2003-05-08 13:19 ` Mirar
2003-05-08 13:31 ` Dieter Nützel
2003-05-15 8:40 ` Mirar
2003-05-15 11:23 ` Dieter Nützel
2003-05-15 15:17 ` Mirar
2003-05-08 18:58 ` Hans Reiser
2003-05-08 19:20 ` Mirar
2003-05-08 19:28 ` Hans Reiser
2003-05-08 19:31 ` Hans Reiser
2003-05-08 19:39 ` Mirar
2003-05-08 12:02 ` Bill Rees
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=200303102115.50039.dirk.leber@web.de \
--to=dirk.leber@web.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.