All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Boylan <ross@biostat.ucsf.edu>
To: Robert Nichols <rnicholsNOSPAM@comcast.net>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] expanding encrypted volume/growing the volume
Date: Wed, 10 Sep 2014 16:47:14 -0700	[thread overview]
Message-ID: <20140910234714.GG8520@markov.biostat.ucsf.edu> (raw)
In-Reply-To: <luqkmt$5em$1@ger.gmane.org>

Thanks for looking things over.
Snapshot info below.
On Wed, Sep 10, 2014 at 05:52:13PM -0500, Robert Nichols wrote:
> On 09/10/2014 05:44 PM, Robert Nichols wrote:
>> Yes, I would merge the snapshot back into the base volume and close the
>> snapshot before extending the filesystem.  Otherwise, the enlarged
>> filesystem structure will exist only in the snapshot.  I suppose an
>> alternative would be to merge the current snapshot, start a new snapshot,
>> and the enlarge the filesystem.  If anything went wrong during the resizing,
>> you could just discard the snapshot and be right back where you were with
>> the filesystem. Merge that snapshot once you've determined that all went
>> well.
>
> ALERT:  I'm thinking of that snapshot backwards, because that's how I most
> often use them (create the snapshot, mount the snapshot instead of the base
> volume, perform the experiment, then throw the snapshot away and mount the
> base volume again to forget the experiment.)
>
> Since I don't know the age or purpose of that snapshot, I don't know whether
> you would want to close it.  It would be a snapshot of the pre-expansion
> filesystem.


These are read-only snapshots created for the backup program.  The
backup program backs up the file system as seen through the snapshot..

It does seem as if it would be easy for something to go wrong if the
snapshot were active while the underlying volume grew.  At a minimum,
growing the file system would presumably use up a lot of space in the
snapshot.

Ross

  reply	other threads:[~2014-09-10 23:47 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
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 [this message]
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=20140910234714.GG8520@markov.biostat.ucsf.edu \
    --to=ross@biostat.ucsf.edu \
    --cc=dm-crypt@saout.de \
    --cc=rnicholsNOSPAM@comcast.net \
    /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.