From: Joe Thornber <thornber@redhat.com>
To: dm-devel@redhat.com
Subject: Interface changes to multisnap
Date: Mon, 20 Jun 2011 13:22:57 +0100 [thread overview]
Message-ID: <20110620122256.GA15181@ubuntu> (raw)
I've just pushed an interface change for multisnap.
From now on the 'new-thin' message to the pool target takes just one
argument, the id of the new device. The size field has been dropped,
instead the new device has a zero size.
When a multisnap target is loaded it implicitly resizes the thin
device based on the size of the target. Truncation will lose data
that is off the end of the new device immediately.
- Joe
https://github.com/jthornber/linux-2.6/tree/multisnap
next reply other threads:[~2011-06-20 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 12:22 Joe Thornber [this message]
2011-06-21 13:59 ` Interface changes to multisnap Joe Thornber
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=20110620122256.GA15181@ubuntu \
--to=thornber@redhat.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.