From: Phillip Susi <psusi@cfl.rr.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Joe Thornber <thornber@redhat.com>
Subject: Re: [linux-lvm] snapshot pools, lvm roadmap
Date: Mon, 10 Jan 2011 10:30:42 -0500 [thread overview]
Message-ID: <4D2B2622.8000902@cfl.rr.com> (raw)
In-Reply-To: <1294654524.2945.9.camel@ubuntu>
On 1/10/2011 5:15 AM, Joe Thornber wrote:
> Are you interested in testing Thin Provisioning too?
I certainly am. I had been using snapshots with --virtualsize for this
to debug e2defrag.
next prev parent reply other threads:[~2011-01-10 15:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 7:11 [linux-lvm] snapshot pools, lvm roadmap Brian Neu
2011-01-05 18:34 ` Brian Neu
2011-01-06 11:59 ` Joe Thornber
2011-01-07 19:33 ` Brian Neu
2011-01-07 20:27 ` Phillip Susi
2011-01-07 20:41 ` Alasdair G Kergon
2011-01-10 10:15 ` Joe Thornber
2011-01-10 15:30 ` Phillip Susi [this message]
2011-01-05 18:45 ` Stuart D. Gathman
2011-01-05 20:56 ` Brian Neu
2011-01-06 16:15 ` Phillip Susi
2011-01-07 1:09 ` Stuart D. Gathman
2011-01-07 19:01 ` Brian Neu
2011-01-08 16:17 ` Stuart D. Gathman
-- strict thread matches above, loose matches on Subject: below --
2011-01-18 15:39 Brian Neu
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=4D2B2622.8000902@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-lvm@redhat.com \
--cc=thornber@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).