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

Re: [Linux-cluster] DLM behavior after lockspace recovery



On Wed, Oct 06, 2004 at 09:15:01AM -0400, Jeff wrote:

> When the value block not valid flag is set any subsequent lock requests
> which read the lock value block complete with a value-block-not-valid
> status. This is a success state. This status continues to be returned
> until the value block is written or the lock is forgotten because it has
> been released by all cluster members.

If VALNOTVALID is returned, do you care what the lvb contents are?

> I'm not sure that implementing this as a flag returned in the lock value
> block is really a good idea as it would mean that interested
> applications would have to perform an extra memory reference for a
> fairly uncommon situation. Should this be implemented as a property of
> the lockspace which is defined when the lockspace is created?

Let's try returning VALNOTVALID in the lksb flags field first and see how
it works.

-- 
Dave Teigland  <teigland redhat com>


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