From owner-freebsd-fs@FreeBSD.ORG Fri Mar 4 14:00:31 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 77721106568D for ; Fri, 4 Mar 2011 14:00:31 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id 6CF518FC1E for ; Fri, 4 Mar 2011 14:00:20 +0000 (UTC) Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta13.westchester.pa.mail.comcast.net with comcast id F1Xe1g0031ei1Bg5D20MPp; Fri, 04 Mar 2011 14:00:21 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta24.westchester.pa.mail.comcast.net with comcast id F20H1g00n0PUQVN3k20HDH; Fri, 04 Mar 2011 14:00:19 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id AF3EF9B422; Fri, 4 Mar 2011 06:00:15 -0800 (PST) Date: Fri, 4 Mar 2011 06:00:15 -0800 From: Jeremy Chadwick To: Dr Josef Karthauser Message-ID: <20110304140015.GA27523@icarus.home.lan> References: <0E00DAFC-C39F-47DC-B9AF-16419C20997F@tao.org.uk> <615F1346-E830-42E2-B229-4181B8BC56BD@exonetric.com> <53FA69D2-2EF0-4CBF-985B-6E710F15FE02@tao.org.uk> <20110302001650.GB49147@icarus.home.lan> <27423168-85BE-41B1-8E14-94F01310EFE4@tao.org.uk> <20110302121612.GA61020@icarus.home.lan> <9EAE56CB-0CE9-4A08-B783-3EF9B1059E62@tao.org.uk> <20110304131849.GA26774@icarus.home.lan> <0A0632A0-24C3-4B11-8542-37A58DCA6390@tao.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0A0632A0-24C3-4B11-8542-37A58DCA6390@tao.org.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Tom Evans , freebsd-fs@freebsd.org Subject: Re: ZFS on a single disk? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2011 14:00:31 -0000 On Fri, Mar 04, 2011 at 01:49:15PM +0000, Dr Josef Karthauser wrote: > On 4 Mar 2011, at 13:18, Jeremy Chadwick wrote: > > > > Not to mention, as I understand it, PAE induces all *sorts* of driver > > incompatibilities and technical hurdles when it comes to the kernel. I > > believe there are features/drivers/etc. which also do not build/work if > > PAE is used in the kernel. If something suddenly starts acting "oddly" > > on a PAE system, it wouldn't surprise me if PAE was to blame. > > > > Joe should be aware that amd64 does offer i386 compatibility libraries > > (referred to as "lib32") so you definitely can run i386 binaries on > > amd64. > > Hey Jeremy, > > I don't believe that that's an issue anymore. The XEN kernel comes > configured with PAE as a default option, and I've seen elsewhere that > there is no technical problems running ZFS in a PAE environment. (The > PAE docs are out of date when they say we can't use kernel modules, > and any 64 bit aware kernel model should run with PAE with no > difficulties). XEN isn't something I'm familiar with, which is obviously a huge part of the problem with me trying to give you advice on the matter. :-) The only virtualisation "system" I'm familiar with is VMware Workstation, which isn't anything like XEN. What I'm going off of is /sys/i386/conf/PAE vs. /sys/i386/conf/XEN. Be sure to notice all the "nodevice" lines in /sys/i386/conf/PAE, and the comment directly above those. The XEN configuration file has "options PAE", which is ultimately what a driver/piece of kernel code would use for compile-time detection for supporting/working under PAE. For example, arcmsr(4) will flat out panic() (intentionally) if PAE is used. bge(4) and twa(4) appear to have a 4GB boundary on DMA; I don't know the implications of this. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB |