From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] expanding encrypted volume/growing the volume
Date: Wed, 10 Sep 2014 08:25:07 -0500 [thread overview]
Message-ID: <lupjfj$h8d$1@ger.gmane.org> (raw)
In-Reply-To: <20140910033131.GD8520@markov.biostat.ucsf.edu>
On 09/09/2014 10:31 PM, Ross Boylan wrote:
> On Tue, Sep 09, 2014 at 08:59:03PM -0500, Robert Nichols wrote:
>> Easy. Create a new LV in that VG and use "--extents 100%FREE" as
>> its size. Fill that LV with whatever variety of random data you
>> choose, then delete that LV and use the space to expand your active
>> LV.
>
> Thanks; I wasn't aware of that syntax.
>
> But do the snapshots make that hazardous? If the maximum space I
> specified for them is pre-allocated it should be fine, but I thought
> the implementation grabbed blocks as needed. If that's the case, a
> snapshot could fail while I have grabbed all the "free" space.
>
> I suppose worst case I could do 90%Free and be good enough.
The snapshot LV can increase its size only if you created it as thinly
provisioned, and even then it can grab extents only within the LV that
you set up as a "thin pool" LV. The space within that thin pool LV is
not "free" for the purposes of creating a new LV. Creating a new LV
with "--extents 100%FREE" will not affect expansion of your snapshot
LVs.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
next prev parent reply other threads:[~2014-09-10 13:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 21:52 [dm-crypt] expanding encrypted volume/growing the volume Ross Boylan
2014-09-09 23:50 ` Arno Wagner
2014-09-10 3:23 ` Ross Boylan
2014-09-10 4:30 ` Ross Boylan
2014-09-10 5:16 ` Arno Wagner
2014-09-10 8:16 ` Ross Boylan
2014-09-10 9:42 ` Arno Wagner
2014-09-10 1:59 ` Robert Nichols
2014-09-10 3:31 ` Ross Boylan
2014-09-10 13:25 ` Robert Nichols [this message]
2014-09-10 20:36 ` Ross Boylan
2014-09-10 22:44 ` Robert Nichols
2014-09-10 22:52 ` Robert Nichols
2014-09-10 23:47 ` Ross Boylan
2014-09-11 4:00 ` Robert Nichols
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='lupjfj$h8d$1@ger.gmane.org' \
--to=rnicholsnospam@comcast.net \
--cc=dm-crypt@saout.de \
/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.