Re: (once again) freebsd-update cron and man whatis

2015-08-11 Thread Matthew Seaman
On 08/11/15 08:21, Marko Cupać wrote: - Next morning I get notification from freebsd-cron for the same update I installed yesterday, but only for /usr/share/man/whatis. (not ok) Did you by any chance happend to run the weekly/320.makewhatis periodic script that night? It is enabled by

(once again) freebsd-update cron and man whatis

2015-08-11 Thread Marko Cupać
Hi, I wrote about this some time ago here on the list: http://marc.info/?l=freebsd-stablem=143556175104543w=3 I am on 10.1-RELEASE-p17 amd64 now, and the problem still remains: - freebsd-update cron fetches new updates and notifies me by email. (ok) - I run freebsd-update install and reboot.

Re: (once again) freebsd-update cron and man whatis

2015-08-11 Thread Marko Cupać
On Tue, 11 Aug 2015 09:31:04 +0100 Matthew Seaman matt...@freebsd.org wrote: On 08/11/15 08:21, Marko Cupać wrote: - Next morning I get notification from freebsd-cron for the same update I installed yesterday, but only for /usr/share/man/whatis. (not ok) Did you by any chance happend

Re: (once again) freebsd-update cron and man whatis

2015-08-11 Thread Michael B. Eichorn
On Tue, 2015-08-11 at 11:48 +0200, Marko Cupać wrote: On Tue, 11 Aug 2015 09:31:04 +0100 Matthew Seaman matt...@freebsd.org wrote: On 08/11/15 08:21, Marko Cupać wrote: - Next morning I get notification from freebsd-cron for the same update I installed yesterday, but only for

Continuously increasing L2ARC header size

2015-08-11 Thread Daniel Genis
Dear FreeBSD community, We're facing a somewhat odd issue, perhaps similar to what is discussed here: https://forums.freebsd.org/threads/l2arc-degraded.47540/ The issue is that the L2ARC header seems to grow without limit, similar to a memory leak, pressuring more and more memory over time out

Re: Continuously increasing L2ARC header size

2015-08-11 Thread Daniel Genis
Hello everyone, looking closer and comparing our servers, we infact have 2 servers that behave differently, but they also have a different workload (mail instead of file storage). They have identical hardware, but were installed at a later time, compared to the servers which do have the issue.