Re: Device-mapper cluster locking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Device-mapper cluster locking
From: Alasdair G Kergon <agk@xxxxxxxxxx>
Date: Wed, 7 Apr 2010 20:07:55 +0100
Cc: device-mapper development <dm-devel@xxxxxxxxxx>
In-reply-to: <Pine.LNX.4.64.1004071332130.20373@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: Mikulas Patocka <mpatocka@xxxxxxxxxx>, device-mapper development <dm-devel@xxxxxxxxxx>
Organization: Red Hat UK Ltd. Registered in England and Wales, number 03798903. Registered Office: Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE.
References: <1270648258.25738.18.camel@xxxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.64.1004071332130.20373@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: device-mapper development <dm-devel@xxxxxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)

That's the point I queried about whether or not it used a NULL lock -
hands the decision about when/if to free resources over to the dlm.

Alasdair

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

References:
- Device-mapper cluster locking
  - From: Jonathan Brassow
- Re: Device-mapper cluster locking
  - From: Mikulas Patocka

Prev by Date: Re: Device-mapper cluster locking
Next by Date: Re: Device-mapper cluster locking
Previous by thread: Re: Device-mapper cluster locking
Next by thread: Re: Device-mapper cluster locking
Index(es):
- Date
- Thread

[Index of Archives] [DM Crypt] [Fedora Desktop] [ATA RAID] [Fedora Marketing] [Fedora Packaging] [Fedora SELinux] [Yosemite Discussion] [KDE Users] [Fedora Docs]

Powered by Linux