archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <>
To: Phillip Susi <>
Cc: LVM general discussion and development <>
Subject: Re: [linux-lvm] Mirror allocation policy
Date: Wed, 6 Jan 2021 14:46:16 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jan 06, 2021 at 09:36:39AM -0500, Phillip Susi wrote:
> Based on the number of extents it said it was looking for, I didn't
> think it was the log that it couldn't place.

It was looking for what it calls 'parallel' extents i.e. extents not on
the same device as the ones belonging to the existing LV being
converted, and, at first sight, it wasn't giving you the option of
overriding that in respect of the log.  Clearly the code could be
improved, but it's a very much a niche case, well outside the
normal way it's expected to be used.


linux-lvm mailing list
read the LVM HOW-TO at

      reply	other threads:[~2021-01-06 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 19:31 [linux-lvm] Mirror allocation policy Phillip Susi
2021-01-05 20:47 ` Alasdair G Kergon
2021-01-05 21:10   ` Phillip Susi
2021-01-06  1:52     ` Alasdair G Kergon
2021-01-06 14:36       ` Phillip Susi
2021-01-06 14:46         ` Alasdair G Kergon [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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