[gpfsug-discuss] Hanging file-systems

[Skylar Thompson]

Despite its name, kswapd isn't directly involved in paging to disk; it's
the kernel process that's involved in finding committed memory that can be
reclaimed for use (either immediately, or possibly by flushing dirty pages
to disk). If kswapd is using a lot of CPU, it's a sign that the kernel is
spending a lot of time to find free pages to allocate to processes.

On Tue, Nov 27, 2018 at 05:53:58PM +0000, Simon Thompson wrote:
> Thanks Sven ???
> 
> We found a node with kswapd running 100% (and swap was off)???
> 
> Killing that node made access to the FS spring into life.
> 
> Simon
> 
> From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of "oehmes at gmail.com" <oehmes at gmail.com>
> Reply-To: "gpfsug-discuss at spectrumscale.org" <gpfsug-discuss at spectrumscale.org>
> Date: Tuesday, 27 November 2018 at 16:14
> To: "gpfsug-discuss at spectrumscale.org" <gpfsug-discuss at spectrumscale.org>
> Subject: Re: [gpfsug-discuss] Hanging file-systems
> 
> 1. are you under memory pressure or even worse started swapping .

> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss


-- 
-- Skylar Thompson (skylar2 at u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine