From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com (ext-mx12.extmail.prod.ext.phx2.redhat.com [10.5.110.17]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p8D0b6Z7001512 for ; Mon, 12 Sep 2011 20:37:06 -0400 Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p8D0b2Af018334 for ; Mon, 12 Sep 2011 20:37:02 -0400 Received: from laptop.localnet (ip136.133.dsl-acs2.pdx.iinet.com [209.20.133.136]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp1.pacifier.net (Postfix) with ESMTPS id 0E9F22CA1F for ; Mon, 12 Sep 2011 17:37:02 -0700 (PDT) From: ben Date: Mon, 12 Sep 2011 17:30:58 -0700 Message-ID: <2097280.qh0eFtcjbt@laptop> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [linux-lvm] liblvm2app improvement suggestions Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: linux-lvm@redhat.com When reading the list of logical volumes using the library it can be really difficult to determine just what type of volume each one really is. The problem is that the attributes field doesn't cover all the possiblities. A volume can be an origin and a mirror or it may be a mirror log that is also a mirror. I have had to resort to parsing the name string for things like "_mlog" to determine what I am dealing with. It would be really helpful to have some functions like: lvm_lv_is_snapshot(const lv_t lv) lvm_lv_is_mirror(const lv_t lv) lvm_lv_is_origin(const lv_t lv) lvm_lv_is_mirror_log(const lv_t lv) lvm_lv_is_mirror_leg(const lv_t lv) and you get the idea. Thank you.