On Fri, 2007-01-19 at 10:49 -0800, Rick Stevens wrote: > On Thu, 2007-01-18 at 21:47 -0500, jack wallen wrote: > > > The problem is that it is an ext3 partition in an LVM partition. SO > > > you can not mount it directly. You would mount something like: > > > > > > mount /dev/VolGroup01/LogVol00 /data > > > > > > Where you may run into a problem is that it may be VolGroup00 > > > instead of VolGroup01 and VolGroup00 is probably being used by the > > > new installation as well. You may want to take a look at the LV > > > tools. (man lvm is a good place to start.) > > > > > > > that is the problem exactly. i just read i might have to unhook the new > > drive, hook up the old drive (by itself), boot, rename the volgroup with > > lvm, and then reattach the new drive. problem is this: the old system > > was 32 bit - the new system is 64 bit. > > Irrelevant. The LVM labels on the various bits don't care about whether > the OS is 32- or 64-bit. Oh, and have you tried "vgsplit NewVolGroupName VolGroup00 /dev/hdb1" to simply move the /dev/hdb1 PV from "VolGroup00" to "NewVolGroupName"? In fact, you might try: vgsplit -v --test NewVolGroupName VolGroup00 /dev/hdb1 to see what it'd do first. It it looks like what you want, then take off the "--test" and give it a whirl. ---------------------------------------------------------------------- - Rick Stevens, Senior Systems Engineer rstevens@xxxxxxxxxxxxxxx - - VitalStream, Inc. http://www.vitalstream.com - - - - You know the old saying--any technology sufficiently advanced is - - indistinguishable from a Perl script - - --Programming Perl, 2nd Edition - ----------------------------------------------------------------------
