Re: F_SETLK fails after recovery

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

 



Will do. Having trouble accessing that system at the moment. I hope to get it later today.

Neale

On Sep 3, 2014, at 12:32 PM, Tan Sri Dato' Eur Ing Adli <white.heron@xxxxxxxxx> wrote:

> 
> Well, gimme the other node log too.
> 
> 
> Sent from my iPhone
> 
>> On Sep 3, 2014, at 12:48 AM, Neale Ferguson <neale@xxxxxxxxxxxxxx> wrote:
>> 
>> The logs from the recovering node are attached. If you need the same from the other node I will get them tonight.
>> 
>>> On Sep 2, 2014, at 12:42 PM, David Teigland <teigland@xxxxxxxxxx> wrote:
>>> 
>>> We need to sort out which nodes are sending/receiving plock data to/from
>>> each other.  The way it's supposed to work, is an existing node is
>>> supposed to write its plock data into a checkpoint, then do
>>> send_plocks_stored() to notify the new node that the data is ready.  The
>>> new node is then supposed to receive_plocks_stored(), and read the plock
>>> data from the checkpoint.
>>> 
>>> I could get a better picture if you save and send the output of
>>> dlm_tool dump > dlm_dump.txt
>>> dlm_tool log_plock > dlm_plock.txt
>>> 
>>> after the problem occurs.
>> 
>> <dlm_log_plock.txt>
>> <dlm_dump.txt>

-- 
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster




[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux