All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Danny Norging <norging@gmx.de>
Cc: reiserfs-list@namesys.com
Subject: Re: 2.4.21 -> 2.4.25 cryptoloop mess
Date: Sun, 9 Jan 2005 13:57:27 +0100	[thread overview]
Message-ID: <20050109125727.GC862@favonius> (raw)
In-Reply-To: <19024.1105271084@www24.gmx.net>

Danny Norging wrote (ao):
> reiserfsck-3.6.19 just finished, still nothing new in lost+found :(
> Thats what I did:
> 
> # losetup /dev/loop0 hdc1decrypted.dump
> # reiserfsck --rebuild-tree -S /dev/loop0 -l reiserfsck-3.6.19.log

This is after you ran this command with the older reiserfsck right? In
that case I would make a new copy and try again with this version on the
fresh copy. It might not make any difference at all though, but can be
worth a try.

I'm afraid (but still no Reiserfs expert) that your first --rebuild-tree
run on the original image (without the -S) did more damage than good.

It seems that the Namesys guys will help you out after the holidays.
They will have better suggestions than I have.

-- 
Humilis IT Services and Solutions
http://www.humilis.net

  reply	other threads:[~2005-01-09 12:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <30550.1102921988@www5.gmx.net>
2005-01-08 14:06 ` 2.4.21 -> 2.4.25 cryptoloop mess Danny Norging
2005-01-08 14:43   ` Sander
2005-01-09 10:08     ` Danny Norging
2005-01-09 11:44       ` Danny Norging
2005-01-09 12:57         ` Sander [this message]
2005-01-10 15:23         ` Vitaly Fertman
2005-01-09 12:42       ` Sander
2005-01-08 20:59   ` Hans Reiser

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=20050109125727.GC862@favonius \
    --to=sander@humilis.net \
    --cc=norging@gmx.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.