From: Marius Vollmer <marius.vollmer@redhat.com>
Date: Tue, 28 Jan 2014 11:20:27 +0200
Message-ID: <87y520o42s.fsf@red.mvo.lan>
MIME-Version: 1.0
Subject: [linux-lvm] Ignoring locks with the lvm2app API
Reply-To: LVM general discussion and development <linux-lvm@redhat.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: LVM general discussion and development <linux-lvm@redhat.com>

Hi,

I find myself in the situation where I want to scan the current LVM2
setup (what volumegroups exist, their logical volumes, etc) without
risking to lock.

That brings me to some questions:

 - What's the worst thing that can happen when ignoring locks while
   listing logical volumes, reading their properties with the lvm2app
   library?  Can I do this in a system daemon?  A crash of my process
   would be OK, as would be getting temprarily inconsistent information.
   Permanent damage to the system configuration would not be OK,
   obviously.

 - How would I actually best go about ignoring locks?  I found some
   comments in lvm2app about "better support for locking control", so I
   guess it is not really supported right now.  I could have a go at
   improving this.  Would that be worthwhile?  Any advice?