Re: get_swap_pager(x) failed

On Wed, 13 Dec 2017 10:34:02 +0800
blubee blubeeme <gurenchan_at_gmail.com> wrote:

> On Wed, Dec 13, 2017 at 5:53 AM, Mark Millard <markmi_at_dsl-only.net> wrote:
> 
> > blubee blubeeme gurenchan at gmail.com wrote on
> > Tue Dec 12 15:58:19 UTC 2017 :
> >  
> > > On Tue, Dec 12, 2017 at 3:34 PM, blubee blubeeme <gurenchan at gmail.com  
> > > >wrote:
> > > > I am seeing tons of these messages while running tail -f  
> > /var/log/messages  
> > > > ============
> > > > Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(25): failed  
> > > . . .  
> > > >  1159 blubee        5  20    0   149M 56876K select  6   1:05   0.00%
> > > > ibus-engine-chewing
> > > >
> > > > ===========
> > > >
> > > > What's with all the swap errors? I am running ZFS and I have 16GB of  
> > ram,  
> > > > how could I be having swap space errors?
> > > >  
> > >
> > > Well I added 4GB of extra swap in /var/tmp/swap0
> > > then added that to my /etc/fstab: md99                    none    swap
> > > sw,file=/var/tmp/swap0,late     0       0
> > >
> > > and those errors went away.  
> >
> > I recommend reviewing bugzilla 206048 (title in part
> > "swapfile usage hangs; swap partition works"):
> >
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206048
> >
> > before using file-system based swap spaces. They have
> > lots of problems with deadlocks. See especially comments
> > #7 and #8 quoting Konstantin Belousov. #8 is just a
> > reference to:
> >
> > https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/
> > kerneldebug-deadlocks.html
> >
> > Comment #3 shows a way to test for the problematical
> > behavior.
> >
> > Using swap partitions avoids the issue.
> >
> > ===
> > Mark Millard
> > markmi at dsl-only.net
> >
> >  
> Thanks for the info, why would I be getting swap errors like that when I
> have 32GB of ram?
> sysctl hw.physmem
> hw.physmem: 34253692928
> 
> That really doesn't make any sense to me... Is it Chromium eating up 32GB+
> of ram?
>

I've asked myself that question also.  alc_at_ gave me a hint.

Try this: sysctl vm.pageout_update_period=0

If it helps, put vm.pageout_update_period=0 into /etc/sysctl.conf.

-- 
Gary Jennejohn