All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Louis Erickson <lerickson@rdwarf.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Erased start of voulme...
Date: Sat, 15 Jan 2005 12:51:44 +0100	[thread overview]
Message-ID: <20050115115144.GC25781@favonius> (raw)
In-Reply-To: <Pine.LNX.4.61.0501140818350.24028@holly.rdwarf.net>

Louis Erickson wrote (ao):
> On Fri, 14 Jan 2005, Sander <sander@humilis.net> wrote:
> > What arguments did you use?
> 
> reiserfsck --check /dev/md2

Good. Then the options Lena suggested will most likely make your data
appear.

> > What version of reiserfsck?
> 
> How do I find that out? It isn't in the help or visible as an option.
> If I ask mkfs.reiserfs it tells me it's 3.x.1b (2002). I suspect it's
> quite old.

Normally with -V, but 3.x.1b is the version and it indeed is very old.
Newest is 3.6.19.

Is this because you use an old distribution, and do you have such an old
kernel too? (sorry if I missed the kernel/distribution).

> Should I build new tools (on another similar machine) and use those
> instead?

Yes. Reiserfsck has seen a _lot_ improvement since then.

> > And what filesystem?
> 
> It's /dev/md2, mounting on /var.

...

> All of this is running on software raid, but the volumes are all up
> and good, and the raid component isn't complaining at all.
> 
> Or is that not the question you're asking?

Well, I meant Reiser3 of Reiser4, but it is Reiser3 most likely.


> On Fri, 14 Jan 2005, Alex Zarochentsev <zam@namesys.com> wrote:
> > reiserfsck --rebuild-sb can re-create the super block.
> 
> I saw that, but it looked dangerous, and I didn't want to try it until
> my copy had finished.

Of course :-)  Perform al your reiserfsck commands on the copy, not on
the original. If somehow the copy action failed you still have the
original, while if you perform all your actions on the original and have
a broken copy, you are lost.

> On Fri, 14 Jan 2005, E.Gryaznova <grev@namesys.com> wrote:
> > I would prefer to do the following :
> > dd if=/dev/problem_partition of=/dev/sparedevice
> > sparedevice can be usual disk partition
> 
> I don't have a spare partition large enough in this system. I have
> done:
> 
> dd if=/dev/problem_partition of=/home/scratch/rescue.dat
> 
> I'll then use the loopback file system to create a device entry for
> that file, and work on that. It was a suggestion made earlier on this
> very mailing list, and it sounded like a wise one to me. If the
> loopback doesn't work, I'll fiddle around with hardware to make a
> spare partition large enough available.

It should be oke.

The rest is answered by Lena :-)


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

  parent reply	other threads:[~2005-01-15 11:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 16:23 Erased start of voulme Louis Erickson
2005-01-15  2:49 ` E.Gryaznova
2005-01-15 11:51 ` Sander [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-14  1:03 Louis Erickson
2005-01-14  7:14 ` Sander
2005-01-14 12:25 ` Alex Zarochentsev
2005-01-14 12:32   ` E.Gryaznova

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=20050115115144.GC25781@favonius \
    --to=sander@humilis.net \
    --cc=lerickson@rdwarf.net \
    --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.