From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: Batch/queue LVM operations
Date: Tue, 1 Aug 2017 20:39:20 +0200 [thread overview]
Message-ID: <6aac428d-2c55-4d7f-4ad1-ebcd3b6f2ca6@redhat.com> (raw)
In-Reply-To: <4c0a5ae7-2da4-7610-5d06-90d990bd41de@redhat.com>
Dne 1.8.2017 v 19:46 Zdenek Kabelac napsal(a):
> Dne 1.8.2017 v 19:24 Eric Wheeler napsal(a):
>> On Fri, 28 Jul 2017, Zdenek Kabelac wrote:
>>
>>> Dne 28.7.2017 v 21:22 Eric Wheeler napsal(a):
>>>> Hello,
>>>>
>>>> Is there an option to batch LVM operations?
>>>>
>>>> For example, I would like to delete 100 thin snapshots without updating
>>>> the vgmeta 100 times.
>>>
>>> You could possibly use --select feature to handle all removals with
>>> just one lvremove command.
>>
>> I tried --select, but there is a long pause between removals so it is
>> clearly doing a metadata operation for each removal.
>>
>> Is it possible to do something like this:
>>
>> 1. Hold a lock (how?)
>> 2. vgcfgbackup -f /my-backup/file --ignorelocking-failure
>> 3. Modify /my-backup/file (remove LVs)
>> 4. dmsetup message pool 0 delete ID (each ID)
>> 5. vgcfgrestore --ignorelocking-failure
>> 6. Release lock
>>
Also what is probably worthy exercise:
If you have thinLVs you want to 'remove' -
Deactivate all such LVs in one 'lvchange -an' command upfront.
Then as next step remove all such LVs with one 'lvremove' command.
Take a timed 'strace -ttt' and measure how much time is spend in actual
'ioctl' and compare with the remaining time spend in lvm2 processing.
Then summarize the output and your time-expectation - possibly open RFE BZ
for it.
Regards
Zdenek
next prev parent reply other threads:[~2017-08-01 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 19:22 Batch/queue LVM operations Eric Wheeler
2017-07-28 19:43 ` Zdenek Kabelac
2017-07-28 21:55 ` Eric Wheeler
2017-07-31 12:16 ` Bryn M. Reeves
2017-08-01 17:24 ` Eric Wheeler
2017-08-01 17:46 ` Zdenek Kabelac
2017-08-01 18:39 ` Zdenek Kabelac [this message]
2017-08-04 0:59 ` Eric Wheeler
2017-08-14 12:36 ` Zdenek Kabelac
2017-08-04 0:38 ` Eric Wheeler
2017-08-14 12:29 ` Zdenek Kabelac
2017-07-31 9:01 ` Germano Percossi
2017-07-31 9:19 ` Zdenek Kabelac
2017-07-31 9:22 ` Germano Percossi
2017-08-01 17:20 ` Eric Wheeler
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=6aac428d-2c55-4d7f-4ad1-ebcd3b6f2ca6@redhat.com \
--to=zkabelac@redhat.com \
--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.