All of lore.kernel.org
 help / color / mirror / Atom feed
From: Germano Percossi <germano.percossi@citrix.com>
To: lvm-devel@redhat.com
Subject: Batch/queue LVM operations
Date: Mon, 31 Jul 2017 10:01:18 +0100	[thread overview]
Message-ID: <fcfc34d4-eb7e-ce89-b83f-39d4fff56cbb@citrix.com> (raw)
In-Reply-To: <alpine.LRH.2.11.1707281919050.9683@mail.ewheeler.net>

Hi,

Not sure if it an option for you but the Python bindings
allow you to instantiate a VG object that will hold the
lock and then issue all the commands you want before
flushing the metadata at the very end.

Cheers,
Germano

On 07/28/2017 08:22 PM, Eric Wheeler wrote:
> 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.
> 
> Same thing with lvcreate, lvresize, etc.  
> 
> If would be neat if `lvm`'s readline prompt could take multiple commands 
> via stdin and commit them once, even at the expense of longer lock times.
> 
> Is there already support for this in some form?
> 
> 
> --
> Eric Wheeler
> 
> --
> lvm-devel mailing list
> lvm-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/lvm-devel
> 



  parent reply	other threads:[~2017-07-31  9:01 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
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 [this message]
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=fcfc34d4-eb7e-ce89-b83f-39d4fff56cbb@citrix.com \
    --to=germano.percossi@citrix.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.