From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Shrinking LVM partition at beginning
Date: Sun, 10 Apr 2016 00:45:58 +0100 [thread overview]
Message-ID: <20160409234558.GI9081@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <57094147.202@redhat.com>
On Sat, Apr 09, 2016 at 07:52:07PM +0200, Zdenek Kabelac wrote:
> Unsupported
The process could easily be automated, but there just isn't enough
demand to justify spending the time writing and testing code for it.
An expert would also find it pretty easy to test each step as they
proceeded without making any irreversible changes that risked data
loss. E.g. using device-mapper to try out the device in advance
of the partition table change with the PV header sectors mapped
somewhere else and using some of the advanced lvm.conf options
that take metadata from elsewhere.
Alasdair
next prev parent reply other threads:[~2016-04-09 23:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 10:12 [linux-lvm] Shrinking LVM partition at beginning Nick Urbanik
2016-04-09 17:52 ` Zdenek Kabelac
2016-04-09 23:45 ` Alasdair G Kergon [this message]
2016-04-09 23:19 ` Alasdair G Kergon
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=20160409234558.GI9081@agk-dp.fab.redhat.com \
--to=agk@redhat.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 NNTP newsgroup(s).