From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] LVM fast mode
Date: Mon, 7 Mar 2022 09:55:08 -0500 [thread overview]
Message-ID: <fec7624b-29de-0a04-0856-fa17800f3c30@invisiblethingslab.com> (raw)
[-- Attachment #1.1.1.1: Type: text/plain, Size: 740 bytes --]
Would it be possible to have a fast, but less-safe mode for lvm2?
Right now lvm2 always enumerates every single block device on
the system, which is hugely wasteful when one knows exactly which
block devices are the PVs that will be affected by the operation.
“Less-safe” means that this is intended for use by programs that
know what they are doing, and that know that e.g. clustering is not
in use. Using this in conjunction with clustering is a bug in the
application. Commands that enumerate devices will, in fast mode, only
return LVs on the provided list of PVs. Attempts to modify an LV on a
different PV would fail as of the LV did not exist.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab
[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 4963 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 202 bytes --]
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next reply other threads:[~2022-03-07 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 14:55 Demi Marie Obenour [this message]
2022-03-07 16:23 ` [linux-lvm] LVM fast mode David Teigland
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=fec7624b-29de-0a04-0856-fa17800f3c30@invisiblethingslab.com \
--to=demi@invisiblethingslab.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 read-only IMAP folder(s) and NNTP newsgroup(s).