Re: Still getting kmem exhausted panic

2010-09-28 Thread Ben Kelly
On Sep 28, 2010, at 9:36 AM, Andriy Gapon wrote: > Well, no time for me to dig through all that history. > arc_max should be a hard limit and it is now. If it ever wasn't then it was a > bug. I believe the size of the arc could exceed the limit if your working set was larger than arc_max. The

Re: Still getting kmem exhausted panic

2010-09-28 Thread Ben Kelly
On Sep 28, 2010, at 12:30 PM, Andriy Gapon wrote: > on 28/09/2010 18:50 Ben Kelly said the following: >> >> On Sep 28, 2010, at 9:36 AM, Andriy Gapon wrote: >>> Well, no time for me to dig through all that history. arc_max should be a >>> hard limit and it is n

Re: Still getting kmem exhausted panic

2010-09-28 Thread Ben Kelly
On Sep 28, 2010, at 1:17 PM, Andriy Gapon wrote: > on 28/09/2010 19:46 Ben Kelly said the following: >> Hmm. My server is currently idle with no I/O happening: >> >> kstat.zfs.misc.arcstats.c: 25165824 >> kstat.zfs.misc.arcstats.c_max: 46137344 >> kstat

Re: Still getting kmem exhausted panic

2010-09-28 Thread Ben Kelly
On Sep 28, 2010, at 5:30 PM, Andriy Gapon wrote: << snipped lots of good info here... probably won't have time to look at it in detail until the weekend >> >> there seems to be a layering violation in that the buffer cache signals >> directly to the upper page daemon layer to trigger page recla

Re: nanobsd build problem

2008-08-18 Thread Ben Kelly
On Mon, 18 Aug 2008 22:14:04 +0300, Dan Pelleg <[EMAIL PROTECTED]> wrote: > I'm trying to build nanobsd. I get the error below. Any ideas? > /usr/src/gnu/lib/libgcc/../../../contrib/gcc/tsystem.h:111:18: error: > time.h: No such file or directory > *** Error code 1 Do you have WITHOUT_TOOLCHAIN

Re: vm.kmem_size settings doesn't affect loader?

2008-09-26 Thread Ben Kelly
On Sep 26, 2008, at 4:43 AM, Bartosz Stec wrote: Jeremy Chadwick wrote: These are the tuning settings I use: vm.kmem_size="1536M" vm.kmem_size_max="1536M" vfs.zfs.arc_min="16M" vfs.zfs.arc_max="64M" Yesterday I've added 512 MB memory to box (sum 1,5GB), and set vm.kmem_size and vm.kmem_size

Re: Possible ZFS livelock or SCHED_ULE bug ?

2009-12-16 Thread Ben Kelly
On Dec 16, 2009, at 11:04 AM, Arnaud Houdelette wrote: > Hi all ! > I got a UniProcessor AMD64 box, with 512 MB ram with 2 ZFS pools as a > home-NAS. > > I got some IO issues since I moved from 7.2 to 8.0. > With a GENERIC kernel (or a stripped down one), during high IO activity (as > a make

Re: ZFS Tuning - arc_summary.pl

2010-03-29 Thread Ben Kelly
On Mar 29, 2010, at 10:43 AM, Barry Pederson wrote: > I've been using the arc_summary.pl script from here: > > http://jhell.googlecode.com/svn/base/head/scripts/zfs/arc_summary/arc_summary.pl > > and noticed some odd numbers, with the ARC Current Size being larger than the > Max Size, and the

Re: Freebsd 8.0 kmem map too small

2010-05-05 Thread Ben Kelly
On May 5, 2010, at 9:33 AM, Pawel Jakub Dawidek wrote: > On Wed, May 05, 2010 at 10:46:31AM +0200, Giulio Ferro wrote: >> On 05.05.2010 09:52, Jeremy Chadwick wrote: >> >> Nope, it's happened again... Now I've tried to rise vm.kmem_size to 6G... >> >> >>> Did you set both vm.kmem_size and vfs.

Re: ZFSKnownProblems - needs revision?

2009-04-12 Thread Ben Kelly
On Apr 8, 2009, at 12:18 PM, Christian Walther wrote: I used geli encrypted ZFS including Root on my IBM Thinkpad T31 with 1GB RAM on a 160GB HDD. (i386 7-STABLE) Swap on a dedicated slice. Some Z Filesystems used compression (/usr/ports, /usr/src, for example). I encountered several crashes, e

Re: ZFSKnownProblems - needs revision?

2009-04-12 Thread Ben Kelly
On Apr 8, 2009, at 5:59 PM, Miroslav Lachman wrote: Rsync is used for "snapshots" with --link-dest= (each day has own directory and all unchenged files are hardlinked to previous day and I have history of two month back). Backups are stored on /vol0 with compression enabled. (compression is

Re: kmem map too small panic after updating to STABLE-7 r192996

2009-06-04 Thread Ben Kelly
On Jun 4, 2009, at 10:48 AM, Tim Chase wrote: vm.kmem_size="512M" vm.kmem_size_max="512M" vfs.zfs.arc_max="100M" $1 = 0xc0792320 "kmem_malloc(131072): kmem_map too small: 325656576 total allocated" It looks like you are suffering from fragmentation of your kmem add

Re: md /tmp mfs rw,-s64m 0 0 in fstab instead of tmpmfs="YES" in rc.conf: no panic

2004-11-10 Thread Ben Kelly
Maybe I'm missing something, but tmpmfs works malloc-based by default. tmpmfs is not an easy way to set up a swap-based ramdisk. It is meant to setup diskless systems easily. One alternative would be to use the ramdisk variables described in rc.conf(5). The only downside is that the ramdisk rc s

missing dependency - crypto.ko to zlib.ko

2006-03-03 Thread Ben Kelly
Hello all, I upgraded my RELENG_6 server today and ran into a strange problem. Whenever I try to kldload crypto.ko the operation fails and I get the following error in my dmesg: link_elf: symbol inflateInit2_ undefined I was indirectly trying to load crypto because I had geom_eli.ko in my

Re: new FreeBSD-webpage

2005-10-06 Thread Ben Kelly
On Thursday 06 October 2005 5:25 am, Claus Guttesen wrote: > Hey. > > Just pointed firefox to freebsd.org and I was greeted with a new look! > Nice work. Overall I like the new site a lot. I did find a broken link however. On: http://www.freebsd.org/community/newsgroups.html The first "newsgro

Re: new FreeBSD-webpage

2005-10-06 Thread Ben Kelly
On Thursday 06 October 2005 5:55 am, Alexander S. Usov wrote: > Claus Guttesen wrote: > > Hey. > > > > Just pointed firefox to freebsd.org and I was greeted with a new look! > > Nice work. > > There are however some small bugs: > if you will press a textsize link in conqueror, then the main menu go

Re: new FreeBSD-webpage

2005-10-06 Thread Ben Kelly
On Thursday 06 October 2005 5:25 am, Claus Guttesen wrote: > Hey. > > Just pointed firefox to freebsd.org and I was greeted with a new look! > Nice work. While I like the new design, I think the mailing list page is a little confusing. There is a prominent section for finding the archives, but n

Re: 5.x: how do I get a *swap*-backed /tmp via rc.conf?

2005-10-10 Thread Ben Kelly
On Monday 10 October 2005 10:55 am, Malcolm Kay wrote: > On Mon, 10 Oct 2005 11:37 am, David Wolfskill wrote: > > I made the somewhat unexpected discovery that in FreeeBSD > > 5-STABLE, if I use the "tmp*" variables in /etc/rc.conf to > > have an MFS /tmp created, it is apparentyly not swap-backed

Re: 5.x: how do I get a *swap*-backed /tmp via rc.conf?

2005-10-10 Thread Ben Kelly
On Monday 10 October 2005 3:49 pm, David Wolfskill wrote: > On Mon, Oct 10, 2005 at 11:03:50AM -0400, Ben Kelly wrote: > > On Monday 10 October 2005 10:55 am, Malcolm Kay wrote: > > > > > > > These paramaters are used by the startup script /etc/rc.d/tmp > &g

RELENG_6 gvinum mirror problem

2005-11-04 Thread Ben Kelly
Hello, I just upgraded my RELENG_5 box to RELENG_6. This machine has two drives mirrored using gvinum. Everything was working well under 5.x, but when I booted to 6.x I noticed only one drive was receiving transactions. I see no error messages in my logs. Running 'gvinum list' produces the

loader.conf setting ignored

2005-11-07 Thread Ben Kelly
Hello all, I am trying to turn on geom debug at boot in order to help figure out my gvinum problem, but I can't seem to set the variable from loader.conf. I can, however, set the variable from the loader prompt. My loader.conf looks like: geom_vinum_load="YES" kern.geom.debugflags="1" I

Re: loader.conf setting ignored

2005-11-07 Thread Ben Kelly
ars this occurs too late to see geom debug for the boot process. (Which makes sense since geom is probably needed to read in sysctl.conf.) I guess this is just something that cannot be done without console access to the loader prompt? Thanks again. > > On Monday 07 November 2005 20:49,

Re: loader.conf setting ignored

2005-11-10 Thread Ben Kelly
Sarxan Elxanzade wrote: It looks like console access is necessary. But may be someone prompt another solution. So it turns out you can set kern.geom.debugflags from loader.conf. The gvinum mirror problem I was trying to debug was causing the problem. Edits to loader.conf were only being writ