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: Re: [linux-lvm] Unusually long boot times with LVM Snapshots
Date: Sat, 21 Nov 2020 13:51:42 +0530	[thread overview]
Message-ID: <CAMaziXuxo6oHSN63T1Jms8kcv3HKVXe_2BtR18g9w=GyNhSFbA@mail.gmail.com> (raw)
In-Reply-To: <20201120111433.GI1787072@localhost.localdomain>

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

On Fri, Nov 20, 2020 at 4:45 PM Bryn M. Reeves <bmr@redhat.com> wrote:

> What type of snapshot are you using? LVM2 allows either "classic" CoW
> snaps,
> or the newer thin provisioned snapshots using the dm-thinp target.
>
> Classic snapshots are known to have very poor IO performance when multiple
> snapshots of the same volume exist simultaneously (especially for write-
> heavy workloads).
>
> Thin provisioned snapshots are not normally activated at boot time unless
> they are explicitly requested (via dracut's rd.lvm.lv options) since they
> have the skip activation flag set by default.
>

I tried thin snapshots, but what use are they if I can't use my system all
together.

Once my root logical volume was marked read only I could not revert it back
to writable, after the snapshot was created.

-- 
Regards,
Sreyan Chakravarty

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

  parent reply	other threads:[~2020-11-21  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 14:16 Sreyan Chakravarty
2020-11-20 11:14 ` Bryn M. Reeves
2020-11-20 16:18   ` Sreyan Chakravarty
2020-11-23 13:13     ` Bryn M. Reeves
2020-11-24 11:57       ` Sreyan Chakravarty
2020-11-25  8:45         ` Sreyan Chakravarty
2020-11-25 12:36         ` Bryn M. Reeves
2020-11-25 15:32           ` Sreyan Chakravarty
2020-11-21  8:21   ` Sreyan Chakravarty [this message]
2020-11-23 12:52     ` Bryn M. Reeves

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='CAMaziXuxo6oHSN63T1Jms8kcv3HKVXe_2BtR18g9w=GyNhSFbA@mail.gmail.com' \
    --to=sreyan32@gmail.com \
    --cc=linux-lvm@redhat.com \
    --subject='Re: [linux-lvm] Unusually long boot times with LVM Snapshots' \
    /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

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