And done.
Technical details: All reiserfs filesystems that were on the host have been replaced with ext3 filesystems, and the host has been converted fully from i386 to amd64. I'll probably update and add some more details on: http://www.wiki.balug.org/wiki/doku.php?id=system:32-bit_to_64-bit But the "up"grade (/crossgrade) from i386 to amd64 went very smoothly (more smoothly than my earlier test run on a scratch test VM to investigate the feasibility/difficulty).
From: "Michael Paoli" Michael.Paoli@cal.berkeley.edu Subject: some intermittent disruptions to some (mostly non-production) BALUG services Date: Sun, 04 May 2014 00:16:56 -0700
Will be doing some system maintenance, so, some ancillary BALUG services will be intermittently unavailable.
Note that this WILL NOT IMPACT: main web site and its pages: http://www.balug.org/ nor our mail lists or email infrastructure.
It WILL IMPACT some other services, at least intermittently, e.g.: http://www.archive.balug.org/ http://www.wiki.balug.org/wiki etc.
Technical details: If it's on 208.96.15.254 it will be impacted. The (qeum-kvm) virtual machine guest on that IP will be undergoing some maintenance: "convert" /usr, /var, and /home filesystems from reiserfs to ext3 (well, actually do a final rsyncs from ro mounted filesystems in single user mode, then switch 'em out and reboot) (and probably also continue up/cross grade from i386 to amd64)