From: Bas van Schaik <bas@tuxes.nl>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Restore LVM snapshot without creating a full dump to an "external" device?
Date: Mon, 10 Mar 2008 10:59:12 +0100 [thread overview]
Message-ID: <47D50670.7030006@tuxes.nl> (raw)
In-Reply-To: <20080309233123.GA6688@racke.local>
Lars Ellenberg wrote:
> On Sun, Mar 09, 2008 at 11:05:45PM +0100, Bas van Schaik wrote:
>
>> Hi all,
>>
>> When I started to use LVM snapshots, I presumed that it was easy to
>> restore a system to such a snapshot. As far as I can see now, this
>> presumption was incorrect... People on the internet write that I should
>> dump the whole snapshot using dd and then write it over the original
>> volume. This actually implies that I need another device with at least
>> the size of the original volume available to dump to. In my situation,
>> this means that I need about 2 TB free space to recover this snapshot!
>>
>> Isn't there a more sophisticated way to restore the snapshot than just
>> dumping it?
>> 1) create snapshot of /dev/myvolumegroup/myvolume to
>> /dev/myvolumegroup/mysnapshot
>> 2) dd if=/dev/myvolumegroup/mysnapshot of=/tmp/mysnapshot.dd
>> 3) lvremove /dev/myvolumegroup/mysnapshot
>> 4) dd if=/tmp/mysnapshot.dd of=/dev/myvolumegroup/myvolume
>>
>
> you got (size-of-your-volume) free space in /tmp?
> pretty large /tmp, or pretty small volume, I guess.
>
>
>> Something like:
>> 1) lvrevert /dev/myvolumegroup/mysnapshot /dev/myvolumegroup/myvolume
>>
>> I'd like to hear your thoughts on this, because I think it should be
>> fairly easy to restore a COW snapshot. Or am I wrong and missing something?
>>
>
> you may want to investigate the status of
> http://fedoraproject.org/wiki/StatelessLinux/CachedClient
> were it says "The LVM and device-mapper code to allow merging is
> awaiting upstream review."
>
Interesting project, interesting information, but it was last updated
2007-10-19. I'll try Googling for a more recent status, if that is
available...
> or you can try, at your own risk, the hack below.
>
> (... lots of excellent details ...)
Sounds very plausible, but there are some risks involved here ;). Thanks
anyhow, I'll really consider using your perl script when the situation
gets critical here...
-- Bas
prev parent reply other threads:[~2008-03-10 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 22:05 [linux-lvm] Restore LVM snapshot without creating a full dump to an "external" device? Bas van Schaik
2008-03-09 23:31 ` Lars Ellenberg
2008-03-10 9:59 ` Bas van Schaik [this message]
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=47D50670.7030006@tuxes.nl \
--to=bas@tuxes.nl \
--cc=linux-lvm@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).