Displaying 3 results from an estimated 3 matches for "nfs4_reclaim_open_state".
2018 Jun 06
3
Firefox and Thunderbird freeze/crash followed by "nfs4_reclaim_open_state: Lock reclaim failed!" syslog messages
...to 7.5, Firefox and
Thunderbird (both 52.8.0, from CentOS repos) regularly freeze (or crash)
and cannot be restarted afterwards. Trying to start them results in a
"Bus error (core dumped)" (Firefox) and "Killed" (Thunderbird). The
system log then shows:
kernel: NFS: nfs4_reclaim_open_state: Lock reclaim failed!
each time I try to start the applications (our homedirectories are
mounted via NFS4). As far as I can see, no other applications are
affected. The workstation needs to be rebooted to fix the situation.
Has anyone else seen that or knows how to debug or fix this issue? I...
2018 Jun 07
0
Firefox and Thunderbird freeze/crash followed by "nfs4_reclaim_open_state: Lock reclaim failed!" syslog messages
...-
> *From:* CentOS <centos-bounces at centos.org> on behalf of James Pearson
> <james-p at moving-picture.com>
> *Sent:* June 6, 2018 2:49 PM
> *To:* CentOS mailing list; Frank Thommen
> *Subject:* Re: [CentOS] Firefox and Thunderbird freeze/crash followed by
> "nfs4_reclaim_open_state: Lock reclaim failed!" syslog messages
> Frank Thommen wrote:
>>
>> Hi,
>>
>> since I updated my workstation from CentOS 7.4 to 7.5, Firefox and
>> Thunderbird (both 52.8.0, from CentOS repos) regularly freeze (or crash)
>> and cannot be restarted after...
2018 Jun 06
0
Firefox and Thunderbird freeze/crash followed by "nfs4_reclaim_open_state: Lock reclaim failed!" syslog messages
...hunderbird (both 52.8.0, from CentOS repos) regularly freeze (or crash)
> and cannot be restarted afterwards.? Trying to start them results in a
> "Bus error (core dumped)" (Firefox) and "Killed" (Thunderbird).? The
> system log then shows:
>
> ???? kernel: NFS: nfs4_reclaim_open_state: Lock reclaim failed!
>
> each time I try to start the applications (our homedirectories are
> mounted via NFS4).? As far as I can see, no other applications are
> affected.? The workstation needs to be rebooted to fix the situation.
>
> Has anyone else seen that or knows how to...