All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Broido <jacob.broido@gmail.com>
To: dm-devel@redhat.com
Subject: Fwd: cow snapshot on cloop device
Date: Wed, 24 Aug 2005 19:01:21 +0200	[thread overview]
Message-ID: <6262291505082410015647272d@mail.gmail.com> (raw)
In-Reply-To: <6262291505082410002ca214a9@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2352 bytes --]

---------- 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

/ # cat /proc/partitions

major minor #blocks name

7 0 loop0
8 0 sda
8 1 sda1
8 2 sda2
8 3 sda3
240 0 cloop0
252 0 dm-0
253 1 dm-1

/ # cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root.old / ext2 rw 0 0
/proc /proc proc rw,noadirtime 0 0
/sys /sys sysfs rw 0 0
/dev/hdc /cdrom iso9660 ro 0 0
/ramdisk /ramdisk tmpfs rw 0 0
/dev/mapper/root_cow0 /cow ext2 rw.noatime 0 0
====================================================

On 8/24/05, Kevin Corry <kevcorry@us.ibm.com> wrote: 
> 
> On Wed August 24 2005 11:35 am, Jacob Broido wrote:
> > Hi,
> > I am trying to set a cow snapshot on a cloop device. 
> > I managed to create a snapshot and mount it as read/write, but it 
> appears
> > that the data inside the /cloop appears invalid:
> >
> > Binary executables appear to be invalid, I perfomed diff between files 
> on 
> > snapshotted /dev/cloop, and the same files accessed directly through 
> cloop.
> >
> > The files were diffrent,
> > anyone has idea as to what can be the reason for this?
> 
> Are you using LVM, EVMS, or dmsetup to create your snapshot? Please send 
> in 
> the output from "dmsetup ls" and "dmsetup table", as well as the contents
> of /proc/partitions and /proc/mounts, after you have activated and mounted
> your snapshot.
> 
> --
> Kevin Corry
> kevcorry@us.ibm.com
> http://www.ibm.com/linux/
> http://evms.sourceforge.net/
> 



-- 
Not gonna be king of the world if you're slave to the grind
- Skid Row 


-- 
Not gonna be king of the world if you're slave to the grind
- Skid Row

[-- Attachment #1.2: Type: text/html, Size: 4200 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2005-08-24 17:01 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     ` Jacob Broido [this message]
2005-08-26  0:02       ` Fwd: " Kevin Corry
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=6262291505082410015647272d@mail.gmail.com \
    --to=jacob.broido@gmail.com \
    --cc=dm-devel@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 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.