Date: Wed, 23 May 2007 21:37:45 +0200 From: Daniel Rock <freebsd@deadcafe.de> To: current@freebsd.org Subject: Re: ZFS committed to the FreeBSD base. Message-ID: <46549809.7040600@deadcafe.de> In-Reply-To: <20070523181903.GA60674@xor.obsecurity.org> References: <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> <20070523093231.GA29797@xor.obsecurity.org> <f31419$bd8$1@sea.gmane.org> <20070523181903.GA60674@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway schrieb: > Not entirely, because solaris also runs on i386 (this is what was > confusing me). I guess the answer is that ZFS has similar issues on > Solaris i386 that it did on FreeBSD i386. Yes, I can confirm that. I'm running 32-bit Solaris 10 with 2GB RAM and occasionally even after only moderate activity on ZFS the machine would hang. ping etc. would still be answered but every filesystem activity would hang. At one instance the machine recovered after approx. 60 minutes, but most of the time I had to hard-reset the machine. In Solaris the solution was simple. Give the kernel more address space. I raised the kernel address space from the default 512MB to 2GB, and now the machine runs stable: eeprom kernelbase=0x80000000 This will reduce the useable address space of user processes though. Daniel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46549809.7040600>