| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Mon, 2004-05-03 at 16:20, Cahill, Ben M wrote:
>
> > -----Original Message-----
> > From: opendlm-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > [mailto:opendlm-devel-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf
> > Of Stanley Wang
> > Sent: Saturday, May 01, 2004 6:34 AM
> > To: OpenDLM-DEV; John T Devine
> > Cc: Zickus II, Don; OpenGFS-DEV
> > Subject: RE: [ogfs-dev]RE: [Opendlm-devel] ODLM/OGFS Recovery
> >
> > Hi John,
> >
> > Thanks for your great comments!
> >
> > On Fri, 2004-04-30 at 15:04, Devine, John T wrote:
> > > Don, locks granted due to the owner of the blocking lock
> > releasing them
> > > due to node failure MUST be granted with an invalidated
> > lock value block
> > > if the blocking mode was PW or stronger. If this is not so, then
> > > unless dead man locks had a mechanism guaranteeing they are
> > granted 1st
> > > (they don't), any OpenDLM user could wind up with a
> > consistency problem
> > > as resources could be granted before node failure detected.
> >
> > It's exactly my concern for OpenGFS.
> >
>
> I think this is handled during ODLM's lock recovery process, which
> invalidates LVBs that might have been altered by a dead node. See
> clmr_clean() and clmr_lkvlb().
Yes, ODLM will invalidate LVBs that might have been altered by a dead
node. But my concern is :
If there is only one PW or EX lock request in the wait queue of this
resource, we won't get DLM_VALNOTVALID (even the LVB of this resouce is
invalid) when the queued request is granted.
It means that we might miss some locks held by dead node. Please read:
rc_barrier6->wake_all_locks->convert_locks->grant_convert->valueblock
Any comments?
Best Regards,
Stan
> -- Ben --
>
> Opinions are mine, not Intel's
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id149&alloc_id66&op=click
> _______________________________________________
> Opendlm-devel mailing list
> Opendlm-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/opendlm-devel
--
Opinions expressed are those of the author and do not represent Intel
Corporation
"gpg --recv-keys --keyserver wwwkeys.pgp.net E1390A7F"
{E1390A7F:3AD1 1B0C 2019 E183 0CFF 55E8 369A 8B75 E139 0A7F}
Attachment:
signature.asc
Description: This is a digitally signed message part