Re: [ClusterLabs] trace of Filesystem RA does not log

2019-10-14 Thread Gang He
> -Original Message- > From: Users [mailto:users-boun...@clusterlabs.org] On Behalf Of Lentes, > Bernd > Sent: 2019年10月14日 20:04 > To: Pacemaker ML > Subject: Re: [ClusterLabs] trace of Filesystem RA does not log > > > >> -Original Message- &g

Re: [ClusterLabs] trace of Filesystem RA does not log

2019-10-14 Thread Lentes, Bernd
>> -Original Message- >> From: Users [mailto:users-boun...@clusterlabs.org] On Behalf Of Lentes, >> Bernd >> Sent: 2019年10月11日 22:32 >> To: Pacemaker ML >> Subject: [ClusterLabs] trace of Filesystem RA does not log >> >> Hi, >&

Re: [ClusterLabs] trace of Filesystem RA does not log

2019-10-14 Thread Lentes, Bernd
- On Oct 14, 2019, at 6:27 AM, Roger Zhou zz...@suse.com wrote: > The stop failure is very bad, and is crucial for HA system. Yes, that's true. > You can try o2locktop cli to find the potential INODE to be blamed[1]. > > `o2locktop --help` gives you more usage details I will try that.

Re: [ClusterLabs] trace of Filesystem RA does not log

2019-10-13 Thread Gang He
Hello Lentes, > -Original Message- > From: Users [mailto:users-boun...@clusterlabs.org] On Behalf Of Lentes, > Bernd > Sent: 2019年10月11日 22:32 > To: Pacemaker ML > Subject: [ClusterLabs] trace of Filesystem RA does not log > > Hi, > > occasionally the

[ClusterLabs] trace of Filesystem RA does not log

2019-10-11 Thread Lentes, Bernd
Hi, occasionally the stop of a Filesystem resource for an OCFS2 Partition fails to stop. I'm currently tracing this RA hoping to find the culprit. I'm putting one of both nodes into standby, hoping the error appears. Afterwards setting it online again and doing the same procedure with the other