[Linux-cluster] GFS2 Errors

[Steven Whitehouse]

Hi,


On 19/07/17 00:39, Digimer wrote:
> On 2017-07-18 07:25 PM, Kristián Feldsam wrote:
>> Hello, I see today GFS2 errors in log and nothing about that is on net,
>> so I writing to this mailing list.
>>
>> node2	19.07.2017 01:11:55	kernel	kern	err	vmscan: shrink_slab:
>> gfs2_glock_shrink_scan+0x0/0x2f0 [gfs2] negative objects to delete
>> nr=-4549568322848002755
>> node2	19.07.2017 01:10:56	kernel	kern	err	vmscan: shrink_slab:
>> gfs2_glock_shrink_scan+0x0/0x2f0 [gfs2] negative objects to delete
>> nr=-8191295421473926116
>> node2	19.07.2017 01:10:48	kernel	kern	err	vmscan: shrink_slab:
>> gfs2_glock_shrink_scan+0x0/0x2f0 [gfs2] negative objects to delete
>> nr=-8225402411152149004
>> node2	19.07.2017 01:10:47	kernel	kern	err	vmscan: shrink_slab:
>> gfs2_glock_shrink_scan+0x0/0x2f0 [gfs2] negative objects to delete
>> nr=-8230186816585019317
>> node2	19.07.2017 01:10:45	kernel	kern	err	vmscan: shrink_slab:
>> gfs2_glock_shrink_scan+0x0/0x2f0 [gfs2] negative objects to delete
>> nr=-8242007238441787628
>> node2	19.07.2017 01:10:39	kernel	kern	err	vmscan: shrink_slab:
>> gfs2_glock_shrink_scan+0x0/0x2f0 [gfs2] negative objects to delete
>> nr=-8250926852732428536
>> node3	19.07.2017 00:16:02	kernel	kern	err	vmscan: shrink_slab:
>> gfs2_glock_shrink_scan+0x0/0x2f0 [gfs2] negative objects to delete
>> nr=-5150933278940354602
>> node3	19.07.2017 00:16:02	kernel	kern	err	vmscan: shrink_slab:
>> gfs2_glock_shrink_scan+0x0/0x2f0 [gfs2] negative objects to delete nr=-64
>> node3	19.07.2017 00:16:02	kernel	kern	err	vmscan: shrink_slab:
>> gfs2_glock_shrink_scan+0x0/0x2f0 [gfs2] negative objects to delete nr=-64
>>
>> Would somebody explain this errors? cluster is looks like working
>> normally. I enabled vm.zone_reclaim_mode = 1 on nodes...
>>
>> Thank you!
> Please post this to the Clusterlabs - Users list. This ML is deprecated.
>
>

cluster-devel is the right list for GFS2 issues. This looks like a bug 
to me, since the object count should never be negative. The glock 
shrinker is not (yet) zone aware, although the quota shrinker is. Not 
sure if that is related, but perhaps.... certainly something we'd like 
to investigate further. That said the messages in themselves are 
harmless, but it will likely indicate a less than optimal use of memory. 
If there are any details that can be shared about the use case, and how 
to reproduce that will be very helpful for us to know. Also what kernel 
version was this?

Steve.