From owner-freebsd-stable@FreeBSD.ORG Fri Feb 13 03:01:40 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 9AF0B106566B for ; Fri, 13 Feb 2009 03:01:40 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 5461D8FC17 for ; Fri, 13 Feb 2009 03:01:40 +0000 (UTC) (envelope-from karl@denninger.net) Received: from [192.168.1.40] (localhost [127.0.0.1]) by FS.denninger.net (8.14.3/8.13.1) with SMTP id n1D31eoq077159 for ; Thu, 12 Feb 2009 21:01:40 -0600 (CST) (envelope-from karl@denninger.net) Received: from [192.168.1.40] [192.168.1.40] by Spamblock-sys (LOCAL); Thu Feb 12 21:01:40 2009 Message-ID: <4994E292.4000802@denninger.net> Date: Thu, 12 Feb 2009 21:01:38 -0600 From: Karl Denninger User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4994CD7B.7040302@denninger.net> <4994D603.2060406@delphij.net> <4994D931.4060508@denninger.net> <4994DACC.1040801@delphij.net> <4994DBC1.2000309@denninger.net> <4994DFB0.3060704@delphij.net> In-Reply-To: <4994DFB0.3060704@delphij.net> Content-Type: multipart/mixed; boundary="------------030301040102000908050404" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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: Fri, 13 Feb 2009 03:01:40 -0000 This is a multi-part message in MIME format. --------------030301040102000908050404 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 but 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* have > 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. > > My personal suggestion is that you do an experiment on another box > (64-bit capable) to make sure that the data would work, this never hurts > and avoids surprises (you do want 64-bit compile of your database > application since you want to take full advantage of 64-bit OS); also, > just like all upgrades, full backup is advised. > > Cheers, > - -- > Xin LI http://www.delphij.net I already know I have to dump the database and then reload it - I attempted to migrate the disk structure across (which would have saved even more time) and got instantaneously hosed, presumably due to internal data type length differences. This little upgrade is going to take a while; sounds like the best approach is to load a new box, shut down the dbms to connections and dump/pipe it over, then physically swap the machines. Thanks. -- -- Karl Denninger karl@denninger.net --------------030301040102000908050404--