From: Oleg Drokin <green@namesys.com>
To: Eugenio Mastroviti <eugeniom@gointernet.co.uk>
Cc: "John O'Donnell" <johnnyo@mindspring.com>, linux-kernel@vger.kernel.org
Subject: Re: Reiserfs has killed my root FS!?!
Date: Tue, 14 May 2002 13:01:54 +0400 [thread overview]
Message-ID: <20020514130153.A817@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205121613430.4369-100000@hawkeye.luckynet.adm> <Pine.GSO.4.21.0205121838230.27629-100000@weyl.math.psu.edu> <20020512225623.GG1020@louise.pinerecords.com> <3CDF1F1B.1090302@mindspring.com> <20020513104615.A10664@namesys.com> <3CDFE8DC.1090803@gointernet.co.uk> <20020513230500.A1897@namesys.com> <3CE0CDC8.1080000@gointernet.co.uk>
Hello!
On Tue, May 14, 2002 at 09:41:44AM +0100, Eugenio Mastroviti wrote:
> >You mean, after the --rebuild-sb command?
> Yes. The first time I ran reiserfsck --rebuild-tree it told me to
> rebuild the superblock and so I ran --rebuild-sb. The startup messages
> only say the format is 3.5.x, so I selected the <=3.5.9 option
This is a mistake.
You need to choose other, more recent format.
It is highly unlikely you might have format of version <=3.5.9
If you have not done rebuild-tree after that again - you may do
--rebuild-sb and choose more recent format, then it should help.
> >What exactly have happened to your FS, BTW?
> A complete - and so far unexplained - system freeze. The distro is SuSE
> 7.3, kernel 2.4.10. I have used it at home ever since it came out
2.4.10 is way too old.
> Well, I'll be very grateful for any insight you can offer
First of all make sure that your raid array same up fully.
This is very important! Check all the partitions if they are of correct size.
Then do rebild-sb and choose more correct superblock version (if asked).
If you are not asked for the fs version, that's bad. Let us know then.
After that you might try to do --rebuild-sb and that one should help.
I see this --rebuild-sb causes a lot of confusion for people, when it asks
the format, I am going to make it to offer some hints.
Thanks for your report.
Bye,
Oleg
next prev parent reply other threads:[~2002-05-14 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 21:29 Reiserfs has killed my root FS!?! Becki Minich
2002-05-12 21:41 ` Diego Calleja
2002-05-12 22:15 ` Thunder from the hill
2002-05-12 22:47 ` Alexander Viro
2002-05-12 22:56 ` Tomas Szepe
2002-05-13 2:04 ` John O'Donnell
2002-05-13 6:46 ` Oleg Drokin
2002-05-13 7:03 ` John O'Donnell
2002-05-13 16:25 ` Eugenio Mastroviti
2002-05-13 19:05 ` Oleg Drokin
2002-05-14 8:41 ` Eugenio Mastroviti
2002-05-14 9:01 ` Oleg Drokin [this message]
2002-05-14 9:28 ` Eugenio Mastroviti
2002-05-13 6:54 ` Frank Schaefer
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=20020514130153.A817@namesys.com \
--to=green@namesys.com \
--cc=eugeniom@gointernet.co.uk \
--cc=johnnyo@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox