From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Unusually long boot times with LVM Snapshots
Date: Mon, 23 Nov 2020 13:13:21 +0000 [thread overview]
Message-ID: <20201123131321.GC2229389@localhost.localdomain> (raw)
In-Reply-To: <CAMaziXss8HAjSjV6g5kFjzkxnYCGZSowfZcT-nJVRm-tf0rJEQ@mail.gmail.com>
On Fri, Nov 20, 2020 at 09:48:10PM +0530, Sreyan Chakravarty wrote:
> How can I check which type of snapshot I am using ?
>
> I am very interested in knowing more about these newer snapshots.
>
> I think I am using the older COW snapshots.
>
> I created it using:
>
> sudo lvcreate -L 70GB -s -n test_snapshot
> /dev/mapper/vgfedora-fedora
This is a classic (aka CoW/copy-on-write or "thick") snapshot since it
was created with a size (-L 70GB). When creating a thin snapshot you do
not specify a size for the snapshot LV - it consumes space from the
associated thin pool as needed.
Generally you can find information about the LVs on your system using
the "lvs" command. The "Attr" field displays lv attributes including the
volume type - see the NOTES section of 'man lvs' for the meaning of the
values. The lvs report can also show you whether a snapshot is using CoW
or thinp and the amount of data it is consuming.
Regards,
Bryn.
next prev parent reply other threads:[~2020-11-23 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 14:16 [linux-lvm] Unusually long boot times with LVM Snapshots 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 [this message]
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
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=20201123131321.GC2229389@localhost.localdomain \
--to=bmr@redhat.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).