From: Oleg Drokin <green@namesys.com>
To: Christian <evilninja@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: vs-4080 & more corruptions
Date: Wed, 26 Jun 2002 09:05:15 +0400 [thread overview]
Message-ID: <20020626090515.B5198@namesys.com> (raw)
In-Reply-To: <3D18FDC8.5040705@gmx.net>
Hello!
On Wed, Jun 26, 2002 at 01:33:28AM +0200, Christian wrote:
> Pass 1 (will try to insert 1109 leaves):
> Looking for allocable blocks .. ok
> 0% left 1079,
> 0 /sec
> mark_block_used: (130815) used already
> Aborted.
> -------
> --> Aborted !? so for now i can't mount the partition:
So far we came to conclusion that this abort is a clear sign of bad memory or
something damaging data that is coming out of your HDD.
It is easily verifiable. Just run reiserfsck --rebuild-tree again
if it progresses to next passes (means you are lucky and nothing
was damaged this time) or fails with different blocknumber "being in use",
you will know that you need to replace some of your hardware.
(may be something as simple as replacing IDE cable).
> root@sheep:~/trash# mount -v /dev/hdb1 /mnt/disk/
> mount: you didn't specify a filesystem type for /dev/hdb1
> I will try type reiserfs
> mount: Not a directory
> huh?
unfinished rebuild tree does this, nothing to worry. Once reiserfsck
--rebuild-tree will correctly complete al its operations you will be able to
mount it again.
> please help me out of this problem, the data was not so important, but:
> i've had more hdd related / fs-related problems during the last year,
> and always after reiserfsck issues. i really want to hold reiserfs the
> faith, because i think it is a good thing to have a performant fs with
> journal too, but i can't stand the problems anymore.
It is impossible to have bad hardware and high stability at the same time
at this level of technology.
Bye,
Oleg
next prev parent reply other threads:[~2002-06-26 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 23:33 vs-4080 & more corruptions Christian
2002-06-26 5:05 ` Oleg Drokin [this message]
2002-06-26 12:03 ` Christian
2002-06-26 13:18 ` Christian
2002-07-02 19:05 ` Kuba Ober
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=20020626090515.B5198@namesys.com \
--to=green@namesys.com \
--cc=evilninja@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.