Re: get_swap_pager(x) failed

2017-12-13 Thread Mark Millard 
On 2017-Dec-13, at 9:43 PM, Peter Jeremy  wrote:

> On 2017-Dec-13 11:23:46 +, Gary Palmer  wrote:
>> An open question would be why ARC is not reducing if the system is
>> under memory pressure.  It's meant to, but there have been various
>> bugs in that implementation.
> 
> The OP doesn't say what version of -current he is running but I would
> point the finger at r325851.  I have discovered that, in 11-stable,
> r326619 (which is the MFC of r325851) stops ARC responding to memory
> backpressure.

See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224080
(bugzialla 224080 ) about problems with zfs from head -r326347 .

bugzilla 224330 is another -r326347 problem report (based on
some list reports) but that are for problems in some non-zfs
contexts.

===
Mark Millard
markmi at dsl-only.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: get_swap_pager(x) failed

2017-12-13 Thread blubee blubeeme 
On Thu, Dec 14, 2017 at 1:43 PM, Peter Jeremy  wrote:

> On 2017-Dec-13 11:23:46 +, Gary Palmer  wrote:
> >An open question would be why ARC is not reducing if the system is
> >under memory pressure.  It's meant to, but there have been various
> >bugs in that implementation.
>
> The OP doesn't say what version of -current he is running but I would
> point the finger at r325851.  I have discovered that, in 11-stable,
> r326619 (which is the MFC of r325851) stops ARC responding to memory
> backpressure.
>
> --
> Peter Jeremy
>

I just did a new install world and kernel so I'm but this is uname -v
FreeBSD 12.0-CURRENT #0 r326839: Thu Dec 14 13:34:47 CST 2017
 root@blubee:/usr/obj/usr/src/amd64.amd64/sys/OSS_GENERIC

The previous was with GENERIC kernel and maybe ports & src from two weeks
ago.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: get_swap_pager(x) failed

2017-12-13 Thread Peter Jeremy 
On 2017-Dec-13 11:23:46 +, Gary Palmer  wrote:
>An open question would be why ARC is not reducing if the system is
>under memory pressure.  It's meant to, but there have been various
>bugs in that implementation.

The OP doesn't say what version of -current he is running but I would
point the finger at r325851.  I have discovered that, in 11-stable,
r326619 (which is the MFC of r325851) stops ARC responding to memory
backpressure.

-- 
Peter Jeremy


signature.asc
Description: PGP signature

Re: get_swap_pager(x) failed

2017-12-13 Thread Gary Palmer 
On Wed, Dec 13, 2017 at 10:34:02AM +0800, blubee blubeeme wrote:
> On Wed, Dec 13, 2017 at 5:53 AM, Mark Millard  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  > > >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 blubee5  200   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: md99noneswap
> > > 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?

Your top output from the first message in the thread gives a hint:

Mem: 3442M Active, 293M Inact, 4901M Laundry, 22G Wired, 1057M Free 
ARC: 18G Total, 1488M MFU, 15G MRU, 4003K Anon, 178M Header, 1171M Other
 16G Compressed, 23G Uncompressed, 1.41:1 Ratio 
Swap: 2048M Total, 2028M Used, 20M Free, 99% Inuse, 36K In  

You have 22GB RAM used by the kernel, and 18GB of that is used by ZFS.
As you can see from the last line, 99% of your small swap space is used
and paging was happening at the time of the snapshot ("36K In").

First I would suggest limiting ARC and seeing if that helps.  Unless you
are doing a lot of fileserver type work or working with lots of files
you want to keep around that ARC size is a bit big.  My desktop with
32GB RAM has ARC limited to 4GB.

Definitely do NOT swap to a file on a filesystem, especially if the
filesystem is ZFS.  That will eventually lead to a deadlock.

An open question would be why ARC is not reducing if the system is
under memory pressure.  It's meant to, but there have been various
bugs in that implementation.

Regards,

Gary
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: get_swap_pager(x) failed

2017-12-12 Thread Gary Jennejohn 
On Wed, 13 Dec 2017 10:34:02 +0800
blubee blubeeme  wrote:

> On Wed, Dec 13, 2017 at 5:53 AM, Mark Millard  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  > > >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 blubee5  200   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: md99noneswap
> > > 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@ 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
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: get_swap_pager(x) failed

2017-12-12 Thread Mark Millard 

On 2017-Dec-12, at 6:34 PM, blubee blubeeme  wrote:

> On Wed, Dec 13, 2017 at 5:53 AM, Mark Millard  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 > > >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 blubee5  200   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: md99noneswap
>> > 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.
> 
> 
> 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'm not familiar with the memory use of the software
that you use. But if swap space is put to use then
file-based swap space is a bad idea from what I
understand. Having no swap space configured is
allowed but may not be sufficient for your context.

In a separate shell window you could monitor what is
going on with something like:

top -Cawores

(You may want a large window.)

That will show something like following in an
updating display:

last pid: 49403;  load averages:  0.13,  0.03,  0.01up 
3+19:28:56  19:33:58
43 processes:  1 running, 42 sleeping
CPU:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
Mem: 1808K Active, 98G Inact, 45M Laundry, 4912M Wired, 1544M Buf, 2462M Free
Swap: 15G Total, 15G Free

  PID USERNAME   THR PRI NICE   SIZERES   SWAP STATE   C   TIME CPU 
COMMAND
  625 root 1  200 55588K 15440K 0K select 15   0:01   0.00% 
/usr/sbin/mountd -r
  627 root 1  520 54024K 14348K 0K select 27   0:00   0.00% 
nfsd: master (nfsd)
. . .

(Some of the detail above is tied to it being a UFS context
instead of a zfs context. There will be zfs information as well
if you are using zfs.)

The SIZE, RES, and SWAP for various processes will give a clue.
Avoid over interpreting: as I understand, these days swapped-out
really means the kernel-stacks for the process are not resident.
The activity is mostly paging activity otherwise. Top does not
track such detailed changes in how it presents information. RES
being zero might not mean what one might expect. Still, the
figures are useful for seeing what is using RAM and the
swapspace.

I'm not aware of a way to find the maximum swapspace in-use-so-far
figure or any estimate of it. Top will display an active in-use
figure if it is in use (not just Total and Free). Of source the
figure is based on periodic sampling. Top does not display the
maximum-observed-so-far of its periodic sampling.

===
Mark Millard
markmi at dsl-only.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: get_swap_pager(x) failed

2017-12-12 Thread blubee blubeeme 
On Wed, Dec 13, 2017 at 5:53 AM, Mark Millard  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  > >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 blubee5  200   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: md99noneswap
> > 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?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: get_swap_pager(x) failed

2017-12-12 Thread Mark Millard 
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  >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 blubee5  200   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: md99noneswap
> 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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: get_swap_pager(x) failed

2017-12-12 Thread blubee blubeeme 
On Tue, Dec 12, 2017 at 3:34 PM, blubee blubeeme 
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
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(22): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(11): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(32): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(25): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(8): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(6): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(32): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
> Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
> Dec 12 15:11:41 blubee kernel:

get_swap_pager(x) failed

2017-12-11 Thread blubee blubeeme 
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
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(22): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(11): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(32): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(25): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(8): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(6): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(32): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(9): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(3): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(20): failed
Dec 12 15:11:41 blubee kernel: swap_pager_getswapspace(18): failed
Dec 12 15:11:41 blubee kernel: