public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John O'Donnell" <johnnyo@mindspring.com>
To: Oleg Drokin <green@namesys.com>, linux-kernel@vger.kernel.org
Subject: Re: Reiserfs has killed my root FS!?!
Date: Mon, 13 May 2002 03:03:56 -0400	[thread overview]
Message-ID: <3CDF655C.8070307@mindspring.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>

Oleg Drokin wrote:
> Hello!
> 
> On Sun, May 12, 2002 at 10:04:11PM -0400, John O'Donnell wrote:
> 
> 
>>I'm sorry.  This IS 2.4.18 - I havent played with 2.5 yet - but thanks 
>>for the warning.
>>This is a Seagate ST39102LW hooked into an Adaptec 29160.
> 
> 
> Ok, if you want your fs back, correct way is to download latest preversion of
> reiserfsprogs (reiserfsprogs-3.x.1c-pre4 for now) from namesys.com ftp site,
> build it somewhere, boot off rescue media of some kind, and then run
> reiserfsck with --rebuild-tree argument (and a path to your partition of
> course). If you cannot build any binaries anywhere, I can send you a binary
> of reiserfsck.
> You problem is that pointer to data block got corrupted and now points
> outside of the partition.
> (notw, if you have some reiserfsck version on your rescue media, it won't
> help you, because this exact problem got fixed only recently)
> 
> Bye,
>     Oleg
> 

Well.......
I sorta DISCOVERED THIS!
But, I bow to Oleg anyway!!!!!!!!!!!!!!!!!!
Great utilities!!!!!!!!!!!!!!!!!!!!!!!

Before seeing this I installed Slack 8.0 on another small partition, downloaded
2.4.18, latest reiser tools from slack's site. I had to so a --rebuild-sb
thought first. Then the rebuild tree.....

Now I am back in Linux heaven!  It just booted.

Oh man these errors freaked me the hell out.
I am still turned off by seeing the $25/per question for support on
namesys.com after clicking on "Support" with NO mention of the mailing list.
I found the mailing list LATER and some useful tips.

My brain kernel paniced!

Root FS backup commences...... :-)

Thank you Oleg!
Johnny O

-- 
=== Never ask a geek why, just nod your head and slowly back away.===
+==============================+====================================+
| John O'Donnell               |                                    |
|  (Sr. Systems Engineer,      | http://johnnyo.home.mindspring.com |
|  Net Admin, Webmaster, etc.) |   E-Mail: johnnyo@mindspring.com   |
+==============================+====================================+


  reply	other threads:[~2002-05-13  7:04 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 [this message]
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
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=3CDF655C.8070307@mindspring.com \
    --to=johnnyo@mindspring.com \
    --cc=green@namesys.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