From: Oleg Drokin <green@namesys.com>
To: Soeren Sonnenburg <sonne@first.gmd.de>
Cc: reiserfs-list@namesys.com
Subject: Re: possible bug - fsck shows perfect results, linux refuses to mount
Date: Mon, 31 Mar 2003 12:41:09 +0400 [thread overview]
Message-ID: <20030331124109.G25533@namesys.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0303311028450.4102-100000@pille>
Hello!
On Mon, Mar 31, 2003 at 10:34:30AM +0200, Soeren Sonnenburg wrote:
> Today a raid0 (stripe set) crashed here (there is a bug in western
> digital disks - they sometimes need a power cycle to accept commands
> again) and I ran the latest reiserfsck on /dev/md0 with --rebuild-sb
> --rebuild-tree.
> It successfully finished rebuilding the tree but now I observe the same
> thing robin observes: I cannot mount the device... so I ran reiserfsck
> /dev/md0 again and it complained that there is no superblock on the
> drive. So I tried to create one with reiserfstune --make-standard-journal
Well, if there is no superblock, it will certainly refuse to mount.
> /dev/md0 but that one just segfaults (unfortunately I have gcc on that
> machine as /usr /var are on the stripeset :-( ).
Is it just segfaults without any messages?
Anything interesting in the logs?
What reiserfsprogs version do you use?
> This is really strange since reiserfsck was really enumerating over all
> the files and everything seemed to be fine after the first rebuild-tree.
Hm, might it be that your harddrive eaten the superblock that it was supposed to write
to disk? ;)
> Hmm, I am running kernel 2.4.21pre6
Hm, new IDE changes? What if you try same stuff on 2.4.20?
Bye,
Oleg
next prev parent reply other threads:[~2003-03-31 8:41 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
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 [this message]
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=20030331124109.G25533@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sonne@first.gmd.de \
/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.