All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marian Csontos <mcsontos@sourceware.org>
To: lvm-devel@redhat.com
Subject: stable-2.02 - build: make generate
Date: Tue, 19 May 2020 09:38:44 +0000 (GMT)	[thread overview]
Message-ID: <20200519093844.F182739540C4@sourceware.org> (raw)

Gitweb:        https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=7ea50a47d15dea016f252a5940c6aa5c0d598bb6
Commit:        7ea50a47d15dea016f252a5940c6aa5c0d598bb6
Parent:        bac7d5951dd3b5b04d4532b342c1034802f0d466
Author:        Marian Csontos <mcsontos@redhat.com>
AuthorDate:    Mon May 11 18:01:15 2020 +0200
Committer:     Marian Csontos <mcsontos@redhat.com>
CommitterDate: Tue May 19 11:38:23 2020 +0200

build: make generate

---
 conf/example.conf.in | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/conf/example.conf.in b/conf/example.conf.in
index 38855e933..29b0df497 100644
--- a/conf/example.conf.in
+++ b/conf/example.conf.in
@@ -326,6 +326,12 @@ devices {
 	# Enabling this setting allows the VG to be used as usual even with
 	# uncertain devices.
 	allow_changes_with_duplicate_pvs = 0
+
+	# Configuration option devices/allow_mixed_block_sizes.
+	# Allow PVs in the same VG with different logical block sizes.
+	# When allowed, the user is responsible to ensure that an LV is
+	# using PVs with matching block sizes when necessary.
+	allow_mixed_block_sizes = 1
 }
 
 # Configuration section allocation.



             reply	other threads:[~2020-05-19  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19  9:38 Marian Csontos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-24  8:52 stable-2.02 - build: make generate Marian Csontos
2019-08-27 15:11 Marian Csontos
2019-03-22 10:01 Marian Csontos

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=20200519093844.F182739540C4@sourceware.org \
    --to=mcsontos@sourceware.org \
    --cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.