From: Stuart D Gathman <stuart@gathman.org>
To: Tilman Vogel <tilman.vogel@gmail.com>
Cc: linux-lvm@lists.linux.dev
Subject: Re: Fwd: pvresize after pvcreate changes PV size: expected?
Date: Mon, 13 Jan 2025 12:43:47 -0500 (EST) [thread overview]
Message-ID: <ab9a43f3-2899-268f-a41e-d6d9b91f4d6@gathman.org> (raw)
In-Reply-To: <CAAbQbbA_gvXzgpmgAM8jun3-8=-EiFdNoKGJTRn0P09+RKA5hg@mail.gmail.com>
On Mon, 13 Jan 2025, Tilman Vogel wrote:
> So, long story short: If I want to know how much space LVM is using
> for the PV such that I can resize the containing block device without
> loss, is it safe to use the value from `pvdisplay`?
I've always been confused by this as well. I just make the containing
block device "extra big" and then let pvresize (or the filesystem
resize) detect the actual space available.
prev parent reply other threads:[~2025-01-13 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 22:21 pvresize after pvcreate changes PV size: expected? Tilman Vogel
2025-01-13 13:46 ` Zdenek Kabelac
[not found] ` <CAAbQbbDGW=Q-NBVdgKqt272VYdYdd_i7Cr8qPLJiS2moSjQMAg@mail.gmail.com>
2025-01-13 16:20 ` Fwd: " Tilman Vogel
2025-01-13 17:43 ` Stuart D Gathman [this message]
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=ab9a43f3-2899-268f-a41e-d6d9b91f4d6@gathman.org \
--to=stuart@gathman.org \
--cc=linux-lvm@lists.linux.dev \
--cc=tilman.vogel@gmail.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).