All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Rudy Zijlstra <rudy@edsons.demon.nl>,
	PFC <lists@boutiquenumerique.com>,
	michael chang <thenewme91@gmail.com>,
	reiserfs-list@namesys.com
Subject: Re: recovering from "rm -rf"
Date: Sat, 06 Aug 2005 19:06:16 -0500	[thread overview]
Message-ID: <42F55078.2030204@slaphack.com> (raw)
In-Reply-To: <42F468CD.9070709@namesys.com>

Hans Reiser wrote:
> David Masover wrote:
> 
> 
>>
>>I'm not sure yet how much I'm willing to pay.  If the Namesys people can
>>help me out, there will certainly be a donation headed their way,
>>
> 
> Nah, for you it is no charge, you have done a lot for us.

What exactly have I done?  I haven't contributed a single line of code,
just ranted on the mailing list for you.

I appreciate it, but I think I will pay you anyway.  $25 for a question
very well answered, and my mother says she'll match it -- which is still
nowhere near what I'd have had to pay to get the other hard drive
repaired.  Does that WorldPay link work?

> Did you try
> what Vitaly advised yet?

Yes, it seems to have worked.  I seem to have all my important files,
except one album of music and the last few episodes of anime -- and I'm
still going through lost+found.  That's really not much of a loss.

By the way, I also discovered a nice trick to avoid making a full disk
backup.  I had a 500 gig RAID array that I was trying to rescue, and the
biggest spare disk I had available was 80 gigs.  So, I used dm_snapshot
to create a writable snapshot, using a loopback file on the 80 gig drive
as the COW device.  I did the fsck on the snapshot, then wrote the
snapshot back to the original device (dd if=snapshot of=orig_device)
once I was sure it worked.  If it hadn't worked, I could have simply
removed the snapshot (dmsetup remove snapshot).

The COW file was a 60 gig sparse file that ended up using only 2 gigs or
so on disk after the fsck.

Be warned, though, that dm_snapshot isn't quite like LVM snapshots, and
only LVM snapshots are documented, while only dm_snapshot will work for
this.  I had to read the source.


  reply	other threads:[~2005-08-07  0:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05 17:23 Reiser4progs-1.0.4-1 issues with gcc-4.0.1 Stef van der Made
2005-08-05 17:27 ` Vladimir V. Saveliev
2005-08-05 20:08   ` recovering from "rm -rf" David Masover
2005-08-05 20:57     ` michael chang
2005-08-05 21:17       ` David Masover
2005-08-05 21:27         ` michael chang
2005-08-05 21:39           ` David Masover
2005-08-05 21:36         ` PFC
2005-08-05 21:44           ` Aaron D. Ball
2005-08-05 21:52             ` PFC
2005-08-05 23:03             ` David Masover
2005-08-07  0:01               ` Aaron D. Ball
2005-08-07  7:16                 ` Rudy Zijlstra
2005-08-05 22:28           ` David Masover
2005-08-05 22:59             ` Rudy Zijlstra
2005-08-05 23:22               ` David Masover
2005-08-06  0:22                 ` michael chang
2005-08-06  1:06                   ` David Masover
2005-08-06  1:22                     ` michael chang
2005-08-06  7:37                 ` Hans Reiser
2005-08-07  0:06                   ` David Masover [this message]
2005-08-07 21:33                     ` michael chang
2005-08-08  6:05                     ` 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=42F55078.2030204@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=lists@boutiquenumerique.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=rudy@edsons.demon.nl \
    --cc=thenewme91@gmail.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.