[prev in list] [next in list] [prev in thread] [next in thread] 

List:       reiserfs-devel
Subject:    (reiserfs) stupidly nuked my reiserfs partition
From:       root <reiser () idiom ! com>
Date:       1999-05-30 17:29:48
[Download RAW message or body]


It is the utils that have the bug.  Upgrade the utils, repair your
partition, and then wait a few days and upgrade the 2.2.7 patch, it also 
has a bug and we pulled it from our web site (we are changing our
testing and release methodology, it should never have been posted.)

Hans

Haukur Hreinsson writes:
 > I'm using reiserfs as a module under 2.2.7, from a
 > reiserfs-patch-to-2.2.7.gz dated May 6. The utils are older,
 > apparently from February 5 (didn't think they were THAT old).
 > 
 > ----- history -----
 > 
 > This looks like it is an old reiser.fsck bug that is now fixed.  Please
 > hang on long enough for Vladimir to wake up, and he'll try to help.
 > Please tell us exactly what version of reiserfs and the utils you are
 > using.
 > 
 > Hans
 > 
 > Haukur Hreinsson writes:
 >  > Let's not go into what exactly I was thinking, but suffice it to say
 >  > that hdparm should be used with caution :-)
 >  > 
 >  > My system locked up hard and on the following reiserfsck, this
 >  > happens:
 >  > 
 >  > <-----------REISERFSCK, version 0.91, 1998----------->
 >  > 
 >  > Pass 1 - 0%....20%....40%....60%....80%.
 >  > bread: lseek to position -2147483648 returned -1 (block=65536, dev=3)
 >  > 
 >  > Thankfully it was only the reiserfs partition that got hosed and not
 >  > the ext2 partitions on the same disk, which contain more valuable
 >  > data.
 >  > 
 >  > Since this is a somewhat dated version of reiserfs, I wonder if
 >  > knowing about reiserfsck's failure is even helpful to developers.
 >  > 
 >  > The data I lost is replacable (gnome cvs checkouts and
 >  > installation), but I would save a good bit of bandwidth if I could
 >  > restore it. Any hints?

[prev in list] [next in list] [prev in thread] [next in thread]