From: michael chang <thenewme91@gmail.com>
To: David Masover <ninja@slaphack.com>
Cc: reiserfs-list@namesys.com
Subject: Re: recovering from "rm -rf"
Date: Sun, 7 Aug 2005 17:33:47 -0400 [thread overview]
Message-ID: <b14e81f005080714337b98765c@mail.gmail.com> (raw)
In-Reply-To: <42F55078.2030204@slaphack.com>
On 8/6/05, David Masover <ninja@slaphack.com> wrote:
> > 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.
Congratulations. Hopefully, you'll have another way to make room for
Windows though [assuming you haven't already] -- if it's not too much
of a pain, I've found some people resort to having disk images (e.g. a
FAT32 image on a Linux Filesystem) and using either VMWare or QEMU...
*sigh* But you'll need a fast machine to get even a semi decent
speed, and the file can be huge (e.g. couple of gigs) and if it gets
fragmented, then performance is a pain (fragemented files on a
fragmented disk image.. uggh, I don't want to think about it).
I guess something to keep in mind on the online resizer -- ability to
handle larger images than free space (if possible) or at least large
files. This, I suppose, could be boasted as a reason to convert e.g.
VMWare users to use Resier4 as an underlying filesystem in the future.
If you make a Windows driver also, [with a decent defragmenter,
online or otherwise, that handles large disk images] then people who
use VMWare surely wouldn't mind paying a couple of bucks to ensure
maximum "performance" from their disks. Just something to consider.
;) [Note: I don't personally use VMWare, but this is my opinion of
their users, considering how expensive VMWare licences are in and of
themselves - a Resier4 driver would probably pale in comparison, and
be considered a bargain. Hopefully.]
--
~Mike
- Just my two cents
- No man is an island, and no man is unable.
next prev parent reply other threads:[~2005-08-07 21:33 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
2005-08-07 21:33 ` michael chang [this message]
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=b14e81f005080714337b98765c@mail.gmail.com \
--to=thenewme91@gmail.com \
--cc=ninja@slaphack.com \
--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.