public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eugenio Mastroviti <eugeniom@gointernet.co.uk>
To: Oleg Drokin <green@namesys.com>
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 09:41:44 +0100	[thread overview]
Message-ID: <3CE0CDC8.1080000@gointernet.co.uk> (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>

Oleg Drokin wrote:

>>Sorry to bother you, but are you sure you spelled it correctly? The 
> 
> I am.

Sorry.

>>I have the same problem on a machine (made worse by the fact that the 
>>filesystem was a RAID0 partition).
>>I keep getting "wrong superblock", even after I told reiserfsck to 
>>rebuild the superblock.
> 
> 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

> 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 
without a single problem, so I'm quite surprised it died after a few 
days of operations just serving a Samba share and acting as a Squid 
proxy at the office (6-7 people using it, not heavy traffic).

The screen was blank and it needed a hard reboot. After the reboot I had 
the same error the initial post reported.

I do not know if the raid0 partition failed in some way and it crashed 
the system, or whether the system froze for some ther reason and the 
hard reboot messed up the partition as well - although I tend to favor 
the second case. I might have forgotten to disable APM, which on a 
number of Dell machines has given me problems (the box is an old Dell 
XPS with a 266 MHz PII). Possibly, APM kicked in and it froze the 
machine - but I'm surprised this happened after over a week of continued 
operations.


Well, I'll be very grateful for any insight you can offer

Eugenio



  reply	other threads:[~2002-05-14  8:53 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 [this message]
2002-05-14  9:01                   ` Oleg Drokin
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=3CE0CDC8.1080000@gointernet.co.uk \
    --to=eugeniom@gointernet.co.uk \
    --cc=green@namesys.com \
    --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