All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: Thorsten Mauch <mauch@imkenberg.de>,
	"'reiserfs-list@namesys.com'" <reiserfs-list@namesys.com>
Subject: Re: rebuild fs
Date: Tue, 05 Aug 2003 16:28:15 +0400	[thread overview]
Message-ID: <3F2FA2DF.3050505@namesys.com> (raw)
In-Reply-To: <20030805104546.GA22557@namesys.com>

Oleg Drokin wrote:

>Hello!
>
>On Tue, Aug 05, 2003 at 12:02:02PM +0200, Thorsten Mauch wrote:
>
>  
>
>>But while rebuilding the tree, I got a segmentation fault. Because I didn't
>>want to continue work on the original raid system, I copied the entire raid
>>disk to the IDE disk.
>>dd  if=/dev/rd/c0d0  of=/dev/hda conv=noerror,sync
>>I tried to rebuild the fs structure again, and  I was able to access many
>>files, but not that are important to me :(
>>Does there is anyting I can do in this state ? does other tools then
>>resierfsck exist ?
>>    
>>
>
>If you are not using latest fsck version (3.6.11 as of now), try to use reiserfsprogs 3.6.11,
>as there is slight chance it would do better.
>
>Bye,
>    Oleg
>
>
>  
>
rephrase that as, use 3.6.11, if it still fails, tell us, the segfault 
will at least be fixed regardless of whether fsck has enough data to do 
its job.

-- 
Hans



  reply	other threads:[~2003-08-05 12:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 10:02 rebuild fs Thorsten Mauch
2003-08-05 10:45 ` Oleg Drokin
2003-08-05 12:28   ` Hans Reiser [this message]
2003-08-05 12:54     ` Oleg Drokin
2003-08-05 12:56       ` Hans Reiser
2003-08-05 13:17         ` Oleg Drokin
2003-08-05 13:28           ` Hans Reiser
2003-08-05 13:35             ` Oleg Drokin
2003-08-05 13:40               ` Hans Reiser
2003-08-05 14:19                 ` Vitaly Fertman
2003-08-05 15:09                   ` Hans Reiser
  -- strict thread matches above, loose matches on Subject: below --
2003-08-05 13:06 Thorsten Mauch

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=3F2FA2DF.3050505@namesys.com \
    --to=reiser@namesys.com \
    --cc=green@namesys.com \
    --cc=mauch@imkenberg.de \
    --cc=reiserfs-list@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.