于 2012/8/15 0:03, Sunil Mushran 写道:
On Mon, Aug 13, 2012 at 7:03 PM, Xue jiufei xuejiu...@huawei.com
mailto:xuejiu...@huawei.com wrote:
A parallel umount on 4 nodes triggered a bug in
dlm_process_recovery_date(). Here’s the situation:
Receiving MIG_LOCKRES message, A node
On Tue, Aug 14, 2012 at 10:03:17AM +0800, Xue jiufei wrote:
A parallel umount on 4 nodes triggered a bug in
dlm_process_recovery_date(). Here’s the situation:
Receiving MIG_LOCKRES message, A node processes the locks in migratable
lockres. It copys lvb from migratable lockres when
On Tue, Aug 14, 2012 at 11:28 PM, Xue jiufei xuejiu...@huawei.com wrote:
Sorry, I haven't described it clearly.
We trigger the BUG() in dlmrecovery.c:1923.
Lockres had copyed lvb from previous valid locks and then meet with
another lock with the EX level.
1907
On Mon, Aug 13, 2012 at 7:03 PM, Xue jiufei xuejiu...@huawei.com wrote:
A parallel umount on 4 nodes triggered a bug in
dlm_process_recovery_date(). Here’s the situation:
Receiving MIG_LOCKRES message, A node processes the locks in migratable
lockres. It copys lvb from migratable lockres
A parallel umount on 4 nodes triggered a bug in dlm_process_recovery_date().
Here’s the situation:
Receiving MIG_LOCKRES message, A node processes the locks in migratable
lockres. It copys lvb from migratable lockres when processing the first valid
lock.
If there is a lock in the blocked
