archive mirror
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <>
To: LVM general discussion and development <>
Subject: Re: [linux-lvm] What is the use of thin snapshots if the external origin cannot be set to writable ?
Date: Wed, 25 Nov 2020 12:38:53 +0000	[thread overview]
Message-ID: <20201125123853.GB2419337@localhost.localdomain> (raw)
In-Reply-To: <>

On Tue, Nov 24, 2020 at 05:29:36PM +0530, Sreyan Chakravarty wrote:
> On Mon, Nov 23, 2020 at 6:34 PM Bryn M. Reeves <> wrote:
> > It means re-installing but if the system is set up to use a thin pool
> > and thin provisioned logical volumes from the start then you can use
> > snapshots without any of the limitations that you've bumped into with
> > external origin devices.
> Do I have to reinstall my system for thin snapshots ?
> Can't I just clone my filesystem and then create a thin pool ?

You can, it's just typically easier for most users to re-install than to
execute the necessary steps to convert the system after the fact.

If you have sufficient space then you can just create a thin pool, copy
your existing file systems into it and then fix up the fstab, grub boot
entries, initramfs and any other configuration that may still reference
the old device names. Once you're finished you can remove the original
volumes and reclaim the space for use by the thin pool.


  parent reply	other threads:[~2020-11-25 12:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21  3:10 [linux-lvm] What is the use of thin snapshots if the external origin cannot be set to writable ? Sreyan Chakravarty
2020-11-23 12:44 ` Gionatan Danti
2020-11-23 13:04 ` Bryn M. Reeves
2020-11-24 11:59   ` Sreyan Chakravarty
2020-11-25  8:46     ` Sreyan Chakravarty
2020-11-25 12:38     ` Bryn M. Reeves [this message]
2020-11-25 15:31       ` Sreyan Chakravarty

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201125123853.GB2419337@localhost.localdomain \ \ \

* 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).