From: Oleg Drokin <green@namesys.com>
To: grobe@gmx.net
Cc: reiserfs-list@namesys.com
Subject: Re: corrupted fs: bitmap does not match to the correct one....
Date: Wed, 15 May 2002 17:08:55 +0400 [thread overview]
Message-ID: <20020515170855.A986@namesys.com> (raw)
In-Reply-To: <3066.1021467577@www49.gmx.net>
Hello!
On Wed, May 15, 2002 at 02:59:37PM +0200, grobe@gmx.net wrote:
> I have a bad problem with my reiserfs. I got a lot of SCSI-errors in the
Hm. SCSI errors are bad, and you have performed everything on the same hardware?
What kind of errors was there, by the way?
> logs, and did a reiserfsck --rebuild-tree. Than, I checked the (hopefuly) fixed
> fs, and now I get errors:
What version of reiserfsprogs was used?
> [...]
> node (9614688) with wrong level (1) found in the tree (should be 3)
> [...a lot of this]
> free block count 70151604 mismatches with a correct one 70141253
> on-disk bitmap des not match to the correct one. 8134442 bytes differ
> If I try to mount the fs, mount tells me "no directory"...
How about more error messages about scsi errors in the logs?
> I have resized the fs in the past, some months ago... is it possible that
> these errors result from a bad resize action? The fs was up for quite a long
Not likely. If you have extended the fs more than 132M in size, you'd
notice if something go wrong instantly.
> just would like to know if there is a chance to restore the fs, or should I
> just take the backup and build a new fs?
There is always a chance, another question (rather important in your case,
it seems) is what option would be faster.
Bye,
Oleg
next prev parent reply other threads:[~2002-05-15 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 12:59 corrupted fs: bitmap does not match to the correct one grobe
2002-05-15 13:08 ` Oleg Drokin [this message]
2002-05-15 13:58 ` grobe
2002-05-15 14:06 ` Oleg Drokin
2002-05-15 15:56 ` grobe
2002-05-15 17:04 ` Valdis.Kletnieks
2002-05-16 5:13 ` Oleg Drokin
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=20020515170855.A986@namesys.com \
--to=green@namesys.com \
--cc=grobe@gmx.net \
--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.