linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Sreyan Chakravarty <sreyan32@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] What is the use of thin snapshots if the external origin cannot be set to writable ?
Date: Sat, 21 Nov 2020 08:40:44 +0530	[thread overview]
Message-ID: <CAMaziXsY6vpQdD+QQzW_1Km+Ltf41tz0G1WG5xAUiMARFWHoyw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 853 bytes --]

I am looking into thin snapshots since the older COW snapshots delay my
boot enormously.

My normal root fs is on a normal "non-thin" volume.

So to make a snapshot I have boot into a live cd environment then set my
root fs volume to read-only and then set it to inactive.

Commands:

       sudo lvchange -pr vgfedora/fedora
       sudo lvchange -an vgfedora/fedora

Now I create the thin snapshot using lvcreate, after that I need to restore
my root LVS to its original state:

     sudo lvchange -ay vgfedora/fedora

      sudo lvchange -prw vgfedora/fedora

This fails with:

            Command on LV vgfedora/fedora uses options that are invalid
with LV parameters: lv_is_external_origin.


I mean what is the point of creating a snapshot if I can't change my
original volume ?

Is there some sort of resolution ?

-- 
Regards,
Sreyan Chakravarty

[-- Attachment #2: Type: text/html, Size: 1340 bytes --]

             reply	other threads:[~2020-11-21  3:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21  3:10 Sreyan Chakravarty [this message]
2020-11-23 12:44 ` [linux-lvm] What is the use of thin snapshots if the external origin cannot be set to writable ? 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
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:
  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=CAMaziXsY6vpQdD+QQzW_1Km+Ltf41tz0G1WG5xAUiMARFWHoyw@mail.gmail.com \
    --to=sreyan32@gmail.com \
    --cc=linux-lvm@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).