Christos Triantafillou wrote: > Hi, > > I am using RHEL 4.5 and DLM 1.0.3 on a 4-node cluster. > > I noticed the following regarding the LVB: > 1. there are two processes: one that sets the LVB of a resource while > holding an EX lock > and another one that has a NL lock on the same resource and is blocked > on a dlm_lock_wait > for getting a CR lock and reading the LVB. > 2. when the first process is interrupted with control-C or killed, the > second process gets > an invalid LVB error. > > It seems that DLM falsely releases the resource after the first process > is gone and then > the second process reads an uninitialized LVB. > > Can you please confirm this error and create a bug report if necessary? I don't know of this bug in particular, though it might be so. Can you raise a bug and put as much information as possible into it please (example programs, sample output, and contents of /proc/cluster/dlm_locks on the master node before and after the incident). Thanks. -- Patrick -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
