On Mon, Aug 06, 2012 at 02:16:39PM -0600, Eric Blake wrote:
> On 08/02/2012 07:09 AM, Daniel P. Berrange wrote:
> > From: "Daniel P. Berrange"
> >
> > Both LVM volumes and SCSI LUNs have a globally unique
> > identifier associated with them. It is useful to be able
> > to query this identifier to
On Fri, Aug 03, 2012 at 04:03:55PM +0100, Daniel P. Berrange wrote:
> On Thu, Aug 02, 2012 at 11:32:14PM -0500, Doug Goldstein wrote:
> > On Thu, Aug 2, 2012 at 8:09 AM, Daniel P. Berrange
> > wrote:
> > > From: "Daniel P. Berrange"
> > >
> > > Both LVM volumes and SCSI LUNs have a globally uniq
On 08/02/2012 07:09 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> Both LVM volumes and SCSI LUNs have a globally unique
> identifier associated with them. It is useful to be able
> to query this identifier to then perform disk locking,
> rather than try to figure out a stable pat
On Thu, Aug 02, 2012 at 11:32:14PM -0500, Doug Goldstein wrote:
> On Thu, Aug 2, 2012 at 8:09 AM, Daniel P. Berrange
> wrote:
> > From: "Daniel P. Berrange"
> >
> > Both LVM volumes and SCSI LUNs have a globally unique
> > identifier associated with them. It is useful to be able
> > to query thi
On Thu, Aug 2, 2012 at 8:09 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> Both LVM volumes and SCSI LUNs have a globally unique
> identifier associated with them. It is useful to be able
> to query this identifier to then perform disk locking,
> rather than try to figure out a st
From: "Daniel P. Berrange"
Both LVM volumes and SCSI LUNs have a globally unique
identifier associated with them. It is useful to be able
to query this identifier to then perform disk locking,
rather than try to figure out a stable pathname.
---
src/util/storage_file.c | 93 +
