All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Vahalik <nick@nsanity.com>
To: Vladimir Saveliev <vs@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiserfs Data Recovery
Date: Wed, 10 Mar 2004 09:08:01 -0600	[thread overview]
Message-ID: <404F2F51.5000205@nsanity.com> (raw)
In-Reply-To: <1078918871.9476.116.camel@tribesman.namesys.com>

Vladimir Saveliev wrote:

>>Are these features tested?  
>>    
>>
>
>Most of these things were added quickly to solve certain user problems.
>To use them one is to understand what they were created for.
>
>  
>
And I guess that isn't documented....

>>Is there any more documentation on them 
>>besides just what's in the comments?
>>    
>>
>
>no.
>  
>

>>  Are there any good sites to read 
>>up some more on reiserfs v3.6 internals? 
>>    
>>
>
>namesys.com had description of reiserfs internals. But now it does not.
>read source code instead
>  
>
Is there a reason?  I grabbed a copy of the whitepaper from archive.org 
and started reading it last night.  Is that information out of date... 
or is it taken down pending the release of Reiserv4?

>> I've become determined to get 
>>this data back.  I've got a couple ideas that I'd like to try but look 
>>at some of these commands I see that some of the things I'd like to 
>>access may already be written.
>>
>>If the problem is that there are sections of my tree missing, why can't 
>>we just chop the bad sections off and salvage the data that is still 
>>there?  Are there any tools that do this?
>>    
>>
>did you try reiserfsck?
>  
>
Yes... with --rebuild-tree, and it aborts after Pass0 every time.  It 
fixes... maybe 10 leaves... and then it finds a bad pointer (or 
something) and dies every time it runs.

Nick Vahalik

  reply	other threads:[~2004-03-10 15:08 UTC|newest]

Thread overview: 27+ 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 [this message]
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       ` Reiserfs Data Recovery (SOLVED) Nick Vahalik
2004-03-15 16:32         ` Vitaly Fertman
  -- strict thread matches above, loose matches on Subject: below --
2004-03-08 14:22 Reiserfs Data Recovery Nick Vahalik
2004-03-08 14:33 ` Philippe Gramoullé
2004-03-08 14:43   ` Nick Vahalik
2004-03-08 14:59     ` Philippe Gramoullé
2004-03-08 16:06       ` Nick Vahalik
2004-03-09  9:28         ` Vitaly Fertman
2004-03-08 18:41 ` Ryan Underwood
     [not found]   ` <404CC8AA.9020405@nsanity.com>
2004-03-08 21:59     ` Ryan Underwood
     [not found]       ` <404CF46B.10000@nsanity.com>
2004-03-09  1:13         ` Ryan Underwood
2004-03-09 21:24           ` Nick Vahalik
2004-03-09 11:36       ` Hans Reiser
2004-03-09 14:42         ` Nick Vahalik
2004-03-09 15:45           ` Hans Reiser
2004-03-09 16:28             ` Nick Vahalik
2004-03-09 18:08             ` Ryan Underwood
     [not found] <20030727153826-191600041>
2003-07-27 23:22 ` reiserfs data recovery Manuel Krause
     [not found] ` <20030727162537-184400041>
2003-07-28  1:27   ` D. Sen
2003-07-28  1:27     ` D. Sen
2003-07-27 22:38 D. Sen
2003-07-27 22:38 ` D. Sen

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=404F2F51.5000205@nsanity.com \
    --to=nick@nsanity.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@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.