From: Kevin Corry <kevcorry@us.ibm.com>
To: dm-devel@redhat.com
Cc: Jacob Broido <jacob.broido@gmail.com>
Subject: Re: Fwd: cow snapshot on cloop device
Date: Thu, 25 Aug 2005 19:02:39 -0500 [thread overview]
Message-ID: <200508251902.39765.kevcorry@us.ibm.com> (raw)
In-Reply-To: <6262291505082410015647272d@mail.gmail.com>
Hi Jacob,
On Wed August 24 2005 12:01 pm, Jacob Broido wrote:
> ---------- Forwarded message ----------
> From: Jacob Broido <jacob.broido@gmail.com>
> Date: Aug 24, 2005 7:00 PM
> Subject: Re: [dm-devel] cow snapshot on cloop device
> To: Kevin Corry <kevcorry@us.ibm.com>
>
> I am using dmsetup directly. and I do the following:
> 1) Create an empty file that will be used as cow backing storage
> 2) losetup the backing file to /dev/loop0
> 3) create a snapshot of main root_device on /dev/loop0
> 4) mount the cow snapshot
>
>
> Here is the info you requested:
> The kernel is a - 2.6.11.10 <http://2.6.11.10> + xen patch.
> =======================================================
> / # dmsetup ls
> root_master (253, 0)
> root_cow0 (253, 1)
> / # dmsetup table
> root_master: 0 4096128 linear 240:0 0
> root_cow0: 0 4096128 snapshot 253:0 7:0 P 8
Ok, this is not going to do what you're expecting it to do. In order to use
snapshotting, you need a snapshot device, and you also need a snapshot-origin
device. The snapshot-origin code is what monitors the I/O path for the origin
device, and performs the copy-on-writes as necessary.
Last summer I did a write-up how you might use dmsetup to create snapshots.
You can read the thread at:
https://www.redhat.com/archives/dm-devel/2004-July/msg00068.html
But in short, it's vastly simpler to just use LVM2 or EVMS to create
snapshots. You should be able to create volumes on your cloop devices using
either set of tools.
Let me know if you have additional questions after reading through the thread
above.
--
Kevin Corry
kevcorry@us.ibm.com
http://www.ibm.com/linux/
http://evms.sourceforge.net/
next prev parent reply other threads:[~2005-08-26 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 11:35 cow snapshot on cloop device Jacob Broido
2005-08-24 13:58 ` Kevin Corry
[not found] ` <6262291505082410002ca214a9@mail.gmail.com>
2005-08-24 17:01 ` Fwd: " Jacob Broido
2005-08-26 0:02 ` Kevin Corry [this message]
2005-08-26 1:51 ` Jacob Broido
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=200508251902.39765.kevcorry@us.ibm.com \
--to=kevcorry@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=jacob.broido@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.