From: Ondrej Kozina <okozina@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Oleksandr Panchuk <panolex@gmail.com>,
Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] Prepend LV
Date: Mon, 10 Sep 2018 18:09:16 +0200 [thread overview]
Message-ID: <f92838ba-1f59-5489-3c26-13cb64ee0b06@redhat.com> (raw)
In-Reply-To: <b227ce32-6612-7604-477d-70f2b46a9543@redhat.com>
On 09/03/2018 04:52 PM, Zdenek Kabelac wrote:
>
> I assume there is already some RFE to provide such support - in terms of
> existing limitation that you need to always prepend whole 'extent' (so i.e.
> with 4MiB extent size - you need to prepend at least 4MiB)
Here it goes: https://bugzilla.redhat.com/show_bug.cgi?id=1609189
Regards
O.
next prev parent reply other threads:[~2018-09-10 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 9:04 [linux-lvm] Prepend LV Oleksandr Panchuk
2018-09-03 10:40 ` Daniel Etter
2018-09-03 11:02 ` Oleksandr Panchuk
2018-09-03 14:52 ` Zdenek Kabelac
2018-09-10 16:09 ` Ondrej Kozina [this message]
2018-09-21 13:07 ` Oleksandr Panchuk
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=f92838ba-1f59-5489-3c26-13cb64ee0b06@redhat.com \
--to=okozina@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=panolex@gmail.com \
--cc=zkabelac@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).