From: Oleg Drokin <green@namesys.com>
To: "Robin H. Johnson" <robbat2@orbis-terrarum.net>
Cc: reiserfs-list@namesys.com
Subject: Re: possible bug - fsck shows perfect results, linux refuses to mount
Date: Mon, 31 Mar 2003 11:34:46 +0400 [thread overview]
Message-ID: <20030331113446.A31858@namesys.com> (raw)
In-Reply-To: <20030331072250.GC22731@cherenkov.orbis-terrarum.net>
Hello!
On Sun, Mar 30, 2003 at 11:22:50PM -0800, Robin H. Johnson wrote:
> The system refused to mount it originally, so I ran just plain
> --fix-fixable. It showed nothing wrong at all. By a fluke of terminals,
> I have a copy of this first output
> [http://www.orbis-terrarum.net/~robbat2/reiserfs/hdb1.first].
> However the system still refused to mount the drive, showing this in
> syslog:
> Mar 30 22:14:22 [kernel] read_super_block: can't find a reiserfs
> filesystem on (dev 03:41, block 64, size 1024)
> Mar 30 22:14:22 [kernel] read_super_block: can't find a reiserfs
> filesystem on (dev 03:41, block 8, size 1024)
This is indeed strange.
> The drive still refused to mount.
> I dug in fsck.reiserfs --help, and saw '--scan-whole-partition'. Tried
> --rebuild-tree with that on. It showed a LOT of stuff about StatDatas,
> and completed successfully.
Well, this is likely to destroy data, but still it should be mountable at the point of
completion.
Can you please make a metadata dump for us?
"debugreiserfs -p /dev/hdb1 | bzip2 -9c >metadata.bz2" and make this file
available for us to download.
> I just find that there is something definetly wrong if fsck says the
> partition is fine, but Linux refuses to mount it. Either this is a bug
> in Linux, or the reiserfsprogs. Either way, somebody has a bug :-)
Sure, and we are interested in resolving the problem.
Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2003-03-31 7:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 7:22 possible bug - fsck shows perfect results, linux refuses to mount Robin H. Johnson
2003-03-31 7:34 ` Oleg Drokin [this message]
2003-03-31 7:49 ` Robin H. Johnson
2003-03-31 8:00 ` Oleg Drokin
2003-03-31 8:34 ` Soeren Sonnenburg
2003-03-31 8:41 ` Oleg Drokin
2003-03-31 8:48 ` Soeren Sonnenburg
2003-03-31 9:02 ` Oleg Drokin
2003-03-31 8:37 ` Robin H. Johnson
2003-03-31 8:56 ` Oleg Drokin
2003-03-31 9:16 ` Robin H. Johnson
2003-03-31 9:24 ` Oleg Drokin
2003-03-31 10:17 ` Robin H. Johnson
2003-03-31 10:36 ` Oleg Drokin
2003-03-31 11:13 ` Robin H. Johnson
2003-03-31 11:33 ` Oleg Drokin
2003-03-31 13:57 ` Oleg Drokin
2003-03-31 16:03 ` 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=20030331113446.A31858@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=robbat2@orbis-terrarum.net \
/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.