From: Vitaly Fertman <vitaly@namesys.com>
To: Moritz Franosch <mail@Franosch.org>, reiserfs-list@namesys.com
Subject: Re: bug: reiserfsck reports "neither new nor old reiserfs format found"
Date: Fri, 25 Oct 2002 17:18:29 +0400 [thread overview]
Message-ID: <200210251718.29370.vitaly@namesys.com> (raw)
In-Reply-To: <m3n0p23lqn.fsf@gateway.askos>
Hi,
> I've installed the system with Suse 8.0, the system booted (many
> times), then hang and I switched off.
>
> The next boot, the kernel paniced with the message
>
> read_super_block: can't find a reiserfs filesystem on (dev 03:02, block 64,
> size 1024)
>
> Thus I've downloaded reiserfsprogs-3.6.3.tar.gz and did
Please take the last 3.6.4 version of reiserfsprogs.
> reiserfsck --check --logfile check.log /dev/hda2
>
> It reported (I've to type from the screen):
>
> reiserfs_open: neither new nor old reiserfs format found on /dev/hda2
> reiserfsck: could not open filesystem on "/dev/hda2"
Your super block got corrupted somehow or you have your partition table
changed so that the blocknumber of the superblock was changed.
To rebuild the corrupted superblock you can use reiserfsck --rebuild-sb.
> "echo $?" reported 0 as exit status, check.log has size 0.
>
> According to the man page, reportig 0 as an exit status in this case
> is a bug:
> man reiserfsck says:
> 2. Run reiserfsck --check --logfile check.log /dev/hda1. If
> reiserfsck --check exits with status 0 it means no errors were
> discovered.
We decided to not provide a special exit code for corrupted super block
to avoid an automation of super block recovery. This is a difficult case
and should be done manually.
>
> Thank you,
>
> Moritz
--
Thanks,
Vitaly Fertman
next prev parent reply other threads:[~2002-10-25 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 9:34 bug: reiserfsck reports "neither new nor old reiserfs format found" Moritz Franosch
2002-10-25 13:18 ` Vitaly Fertman [this message]
2002-10-25 19:54 ` Moritz Franosch
2002-10-26 0:07 ` Hans Reiser
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=200210251718.29370.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=mail@Franosch.org \
--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.