From: Mr Dash Four <mr.dash.four@googlemail.com>
To: dm-devel@redhat.com
Subject: DM_snapshot_cow filesystem (dmsetup create snapshot)
Date: Sat, 29 Oct 2011 12:19:13 +0100 [thread overview]
Message-ID: <4EABE131.8010706@googlemail.com> (raw)
As part of my livecd data structure dmsetup is used to create a snapshot
containing xz-compressed root combined with copy-on-write ram-based
overlay.
The way as I understand it, the ram-based overlay contains only the
"chunks" of data which is changed. Is there a way - in terms of a tool
or by any other means - to look at this overlay to see what data has
been changed exactly?
I have tried, rather naively as it turned out, to mount the ram-based
overlay but received "unknown filesystem type 'DM_snapshot_cow'" error
message, which makes me thing that the data structure is unique somehow
and private to the device mapper.
One other thing - my dmsetup man page is from 2006 (created some 5 years
ago) even though I am using the latest device-mapper package (1.02.63 I
believe) and this man page does not contain any information on dmsetup
create snapshot format, which is very annoying. Is there an updated
version of the man page I could look at?
next reply other threads:[~2011-10-29 11:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 11:19 Mr Dash Four [this message]
2011-10-29 20:49 ` DM_snapshot_cow filesystem (dmsetup create snapshot) Alasdair G Kergon
2011-11-27 22:31 ` Frederick Grose
2011-11-28 1:08 ` Douglas McClendon
2011-11-29 6:22 ` Frederick Grose
2011-11-30 2:09 ` Douglas McClendon
2011-11-30 21:48 ` Frederick Grose
2011-11-30 22:03 ` Alasdair G Kergon
2011-11-30 23:34 ` Douglas McClendon
2011-12-01 14:12 ` Alasdair G Kergon
2011-12-01 20:18 ` Douglas McClendon
2011-12-01 20:20 ` Alasdair G Kergon
2011-12-01 20:26 ` Douglas McClendon
2011-12-02 3:44 ` Douglas McClendon
2011-12-02 8:46 ` Alasdair G Kergon
2011-12-02 17:42 ` Frederick Grose
2011-12-01 20:21 ` Douglas McClendon
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=4EABE131.8010706@googlemail.com \
--to=mr.dash.four@googlemail.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.