All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Vahalik <nick@nsanity.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiserfs Data Recovery (SOLVED)
Date: Mon, 15 Mar 2004 09:48:52 -0600	[thread overview]
Message-ID: <4055D064.1000604@nsanity.com> (raw)
In-Reply-To: <200403130001.57937.vitaly@namesys.com>

Alright, so apparently it was the hardware... I'm not quite sure how, 
exactly, but something appears to be up.  I borrowed a 200 G drive and 
just dd'ed /dev/sda to /dev/sdb, and then reiserfscked /dev/sdb1... it 
took a lot longer, but when It finished it got through pass 4 completely 
and  had finished.  It had 6430 leaves it couldn't place, so they were 
put in lost+found, and most (85%) of the files are completely intact, 
but some of the bigger ones (divx/iso) were pretty tore up.  I also have 
a couple of files that nautilus thinks are 1.5 exabytes, yes exabytes. 

It still amazes me that even after both the drives completely passed the 
DFT, they are still acting strange.  Heh, silly Hitachi drives.

Thanks for your time, guys.

Nick Vahalik

  parent reply	other threads:[~2004-03-15 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10  3:07 Reiserfs Data Recovery Nick Vahalik
2004-03-10 11:41 ` Vladimir Saveliev
2004-03-10 15:08   ` Nick Vahalik
2004-03-10 15:26     ` Vladimir Saveliev
2004-03-10 16:54       ` Nick Vahalik
     [not found]         ` <200403111419.31982.vitaly@namesys.com>
2004-03-11 15:48           ` Nick Vahalik
2004-03-13  9:44   ` Stewart Smith
     [not found] ` <200403111936.01548.vitaly@namesys.com>
     [not found]   ` <40509A74.6080703@nsanity.com>
     [not found]     ` <200403130001.57937.vitaly@namesys.com>
2004-03-15 15:48       ` Nick Vahalik [this message]
2004-03-15 16:32         ` Reiserfs Data Recovery (SOLVED) Vitaly Fertman

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=4055D064.1000604@nsanity.com \
    --to=nick@nsanity.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vitaly@namesys.com \
    /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.