From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane.org>
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Thu, 11 Sep 2014 00:52:30 +0200 (CEST)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <glkdd-dm-crypt@m.gmane.org>) id 1XRqkX-0006w6-92
 for dm-crypt@saout.de; Thu, 11 Sep 2014 00:52:29 +0200
Received: from c-24-14-20-249.hsd1.il.comcast.net ([24.14.20.249])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Thu, 11 Sep 2014 00:52:29 +0200
Received: from rnicholsNOSPAM by c-24-14-20-249.hsd1.il.comcast.net with local
 (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Thu, 11 Sep 2014 00:52:29 +0200
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
Date: Wed, 10 Sep 2014 17:52:13 -0500
Message-ID: <luqkmt$5em$1@ger.gmane.org>
References: <20140909215203.GG26856@markov.biostat.ucsf.edu>
 <luob98$vk5$1@ger.gmane.org> <20140910033131.GD8520@markov.biostat.ucsf.edu>
 <lupjfj$h8d$1@ger.gmane.org> <20140910203650.GF8520@markov.biostat.ucsf.edu>
 <luqk85$bo$1@ger.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <luqk85$bo$1@ger.gmane.org>
Subject: Re: [dm-crypt] expanding encrypted volume/growing the volume
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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.

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.