>>> On Wed, Sep 12, 2007 at 6:49 AM, in message <[EMAIL PROTECTED] >, Bertil Starck <[EMAIL PROTECTED]> wrote: -snip- > I'm trying to migrate LVM-disks from SLES8 to SLES10, but using Yast in > SLES10 to mount the LVM disks will not work.
The first reaction I had was "LVM versus LVM2." Not sure why that should be a problem, but... > This is the message in Yast: > > "Error > Failure occurred during following action: > Mounting /dev/vg00/vg00 to /slask2 Is vg00 really the name of the Logical Volume as well as the Volume Group? Kind of an usual naming convention. > System error code was: -3003 > > mount -t none /dev/vg00/vg00 /slask2 > mount: unknown filesystem type 'none" Did this come out of YaST, or did you type in the command with "-t none?" > Just typing in the mount-command will get this: > > cslinux03:~ # mount /dev/vg00/vg00 /slask2 > mount: you must specify the filesystem type This means that mount can't figure out the file system type from examination of what it thinks is the superblock. > This is how I exported the LVM-disk from SLES8: > > lnx1:~ # pvscan > pvscan -- reading all physical volumes (this may take a while...) > pvscan -- ACTIVE PV "/dev/dasd/0154/part1" of VG "vg00" [20 MB / 12 > MB free] OOh. You're using devfs. Yuck. > pvscan -- ACTIVE PV "/dev/dasd/0155/part1" of VG "vg00" [20 MB / 12 > MB free] > pvscan -- ACTIVE PV "/dev/dasd/0156/part1" of VG "vg00" [20 MB / 12 > MB free] I'm guessing (but would like you to confirm) that all the LVs in vg00 were umounted before issuing the vgchange and vgexport commands. > lnx1:~ # vgchange -a n vg00 > vgchange -- volume group "vg00" successfully deactivated > lnx1:~ # vgexport vg00 > vgexport -- volume group "vg00" sucessfully exported > lnx1:~ # pvscan > pvscan -- reading all physical volumes (this may take a while...) > pvscan -- inactive PV "/dev/dasd/0154/part1" is in EXPORTED VG "vg00" [20 > MB / 12 MB free] > pvscan -- inactive PV "/dev/dasd/0155/part1" is in EXPORTED VG "vg00" [20 > MB / 12 MB free] > pvscan -- inactive PV "/dev/dasd/0156/part1" is in EXPORTED VG "vg00" [20 > MB / 12 MB free] > lnx1:~ # lvscan > lvscan -- no volume groups found > lnx1:~ # vgscan > vgscan -- reading all physical volumes (this may take a while...) > vgscan -- found exported volume group "vg00PV_EXP" > Now in SLES10: > cslinux03:~ # uname -r > 2.6.16.21-0.8-default > cslinux03:~ # pvscan > PV /dev/dasdi1 is in exported VG vg00 [20.00 MB / 12.00 MB free] > PV /dev/dasdj1 is in exported VG vg00 [20.00 MB / 12.00 MB free] > PV /dev/dasdk1 is in exported VG vg00 [20.00 MB / 12.00 MB free] > cslinux03:~ # vgimport vg00 > Volume group "vg00" successfully imported > As I do not see the /dev/vg00 I enter Yast to add the Volume Group and > add the Physical Volume and the add the Logical Volumes that now appear as > /dev/vg00/vg00 to a mountpoint as /slask2. I would have run the vgscan (and perhaps lvscan) command after the vgimport and before this point. You may also need to do a "vgchange -a y vg00" as well. > But I am not able to mount the LVM-disk as expected! > Anyone having hints in this case? If using YaST to create another vg00, and LV(s) didn't wipe out the metadata on the disks, you might be OK. If it did, you might be very dead in the water. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
