From owner-freebsd-stable@FreeBSD.ORG Wed Feb 18 17:46:28 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B70FB1065672 for ; Wed, 18 Feb 2009 17:46:28 +0000 (UTC) (envelope-from ianjhart@ntlworld.com) Received: from queueout04-winn.ispmail.ntl.com (queueout04-winn.ispmail.ntl.com [81.103.221.58]) by mx1.freebsd.org (Postfix) with ESMTP id 622D98FC0C for ; Wed, 18 Feb 2009 17:46:24 +0000 (UTC) (envelope-from ianjhart@ntlworld.com) Received: from aamtaout02-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout01-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090218172824.HUOZ2989.mtaout01-winn.ispmail.ntl.com@aamtaout02-winn.ispmail.ntl.com> for ; Wed, 18 Feb 2009 17:28:24 +0000 Received: from cpc1-cove3-0-0-cust909.sol2.cable.ntl.com ([86.20.31.142]) by aamtaout02-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090218172823.CXHW21638.aamtaout02-winn.ispmail.ntl.com@cpc1-cove3-0-0-cust909.sol2.cable.ntl.com> for ; Wed, 18 Feb 2009 17:28:23 +0000 X-Virus-Scanned: amavisd-new at cpc2-cove3-0-0-cust311.sol2.cable.ntl.com Received: from gamma.private.lan (gamma.private.lan [192.168.0.12]) by cpc1-cove3-0-0-cust909.sol2.cable.ntl.com (8.14.3/8.14.3) with ESMTP id n1IHSHlr032010 for ; Wed, 18 Feb 2009 17:28:17 GMT (envelope-from ianjhart@ntlworld.com) From: ian j hart To: freebsd-stable@freebsd.org Date: Wed, 18 Feb 2009 17:28:16 +0000 User-Agent: KMail/1.9.10 References: <4994CD7B.7040302@denninger.net> <499526E9.3090804@bit0.com> <2CA7DE699281AFA5DF2BD851@syn> In-Reply-To: <2CA7DE699281AFA5DF2BD851@syn> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200902181728.16842.ianjhart@ntlworld.com> X-Cloudmark-Analysis: v=1.0 c=1 a=C1J2tzzPd2oA:10 a=e78F3LAMAAAA:8 a=yuk-rqkyAAAA:8 a=6I5d2MoRAAAA:8 a=G65KC7RlAAAA:8 a=y5GVXGEQB45XpRBdnEoA:9 a=q8D-5ZZrnAuh5Wpz-rYA:7 a=VSG4XMKYYasVBtt9Lplq4A9k_VEA:4 a=LY0hPdMaydYA:10 a=gJKXwAQIE-YA:10 a=VccRq9qsm4EA:10 a=SV7veod9ZcQA:10 a=1QG0cS6IHSAA:10 Subject: Re: Upgrade from 32-bit to AMD-64? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2009 17:46:29 -0000 On Friday 13 February 2009 08:40:27 Goran Lowkrantz wrote: > Hi, > > When have done this, MySQL is OK but Berkley and PostgreSQL need > dump/restore. > > /glz [sorry I'm a bit late] IIRC system accounting did weird stuff until I adjusted it with rm :) > > --On February 13, 2009 2:53:13 -0500 Mike Andrews wro= te: > > Xin LI wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> Karl Denninger wrote: > >> [...] > >> > >>> I guess I need to schedule the 2-3 hours of downtime..... the reason > >>> for this, by the way, is that I have a dbms app on there that is > >>> getting too RAM hungry for its own good (its a Quadcore CPU) and I'm = up > >>> against the RAM limit for 32-bit code. The board will support more b= ut > >>> 32-bit code won't; ergo, the only way to get beyond this is to go to > >>> 64-bit. > >> > >> Oh wait! One thing you wanted to know is that, some database *can* ha= ve > >> different on-disk format for 32-bit and 64-bit binaries. Be sure to > >> have a dump handy. Last time I hit this on a MySQL "upgrade" between > >> two servers, and I end up using its replication functionality. The > >> operation took longer time than I expected at the beginning. > > > > For what it's worth, I did an in-place source upgrade on our MySQL serv= er > > (for the same lack-of-memory reason) and didn't have any on-disk format > > problems. In fact later on when troubleshooting data corruption proble= ms > > that turned out to be bad hardware, I switched between 32-bit and 64-bit > > mysqld binaries without rebooting or dumping/reimporting the database. > > > > BUT... there was no replication involved. It wouldn't surprise me if t= he > > binlog or relay logs were in an architecture specific format. InnoDB and > > MyISAM tables don't appear to be. This was over a year ago though, so > > test on a scratch box first and you may save yourself a bit of downtime. > > > > The upgrade is a pain, and does have a lot of potential foot-shooting, > > and you have to immediately recompile ALL of your installed ports (and > > anything else not built from ports) to avoid mixing 32-bit and 64-bit > > shared libraries... and that rebuilding ports time is where most of yo= ur > > downtime comes from if it's a production box. > > > > If you're feeling lucky, the procedure's in the list archives somewhere > > and the super-short version is you turn your swap partition into a > > temporary amd64 root filesystem, installworld/kernel into that, boot in= to > > that, then mount and installworld/kernel on top of the old i386 root > > filesystem from there, then boot into it and recompile all your ports > > (after reclaiming your swap partition for swap). Or, the way I did it > > last time was to boot into a PXE diskless FreeBSD/amd64 install and use > > that to mount/install over the i386 stuff. > > > > Definitely practice on a scratch system first. :) > > > > > > -- > > Mike Andrews > > Server Monkey > > Fark, Inc > > mandrews@fark.com > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g" > > ................................................... the future isMobile > > Goran Lowkrantz > System Architect, isMobile AB > Sandviksgatan 81, PO Box 58, S-971 03 Lule=E5, Sweden > Mobile: +46(0)70-587 87 82 > http://www.ismobile.com ............................................... > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" =2D-=20 ian j hart