Results from the scan commands: [EMAIL PROTECTED] dev]# pvscan Found duplicate PV 16aDZnp0DyR9MAfGCRkPM8RSMBI49PDY: using /dev/dasdb2 not /dev/dasda2 PV /dev/dasdb2 VG VolGroup00 lvm2 [6.75 GB / 32.00 MB free] Total: 1 [6.75 GB] / in use: 1 [6.75 GB] / in no VG: 0 [0 ] [EMAIL PROTECTED] dev]# vgscan Reading all physical volumes. This may take a while... Found duplicate PV 16aDZnp0DyR9MAfGCRkPM8RSMBI49PDY: using /dev/dasdb2 not /dev/dasda2 Found volume group "VolGroup00" using metadata type lvm2 [EMAIL PROTECTED] dev]# lvscan Found duplicate PV 16aDZnp0DyR9MAfGCRkPM8RSMBI49PDY: using /dev/dasdb2 not /dev/dasda2 ACTIVE '/dev/VolGroup00/LogVol00' [6.47 GB] inherit ACTIVE '/dev/VolGroup00/LogVol01' [256.00 MB] inherit
[EMAIL PROTECTED] dev]# pvdisplay /dev/dasdb2 Found duplicate PV 16aDZnp0DyR9MAfGCRkPM8RSMBI49PDY: using /dev/dasda2 not /dev/dasdb2 Found duplicate PV 16aDZnp0DyR9MAfGCRkPM8RSMBI49PDY: using /dev/dasdb2 not /dev/dasda2 --- Physical volume --- PV Name /dev/dasdb2 VG Name VolGroup00 PV Size 6.75 GB / not usable 0 Allocatable yes PE Size (KByte) 32768 Total PE 216 Free PE 1 Allocated PE 215 PV UUID 16aDZn-p0Dy-R9MA-fGCR-kPM8-RSMB-I49PDY Looks like the volume groups have the same name. Is there any way around that? Russ Jones -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Wednesday, January 17, 2007 10:56 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR That's Red Hat putting the root file system on an LVM logical volume. Ugh. I hate when that is done. You might have a shot at getting something to mount if you do this for starters: pvscan vgscan lvscan If LVM finds the logical volume, and there aren't any conflicts, it might create a device node for it. You should then be able to mount the resulting logical volume. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Russell Sent: Wednesday, January 17, 2007 9:40 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR The df command shows the following: [EMAIL PROTECTED] dev]# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroup00-LogVol00 6676408 1430704 4906556 23% / /dev/dasda1 99168 14560 79492 16% /boot none 61260 0 61260 0% /dev/shm The following are present in the /dev directory: brw-rw---- 1 root disk 94, 0 Jan 16 11:37 dasda brw-rw---- 1 root disk 94, 1 Jan 16 11:37 dasda1 brw-rw---- 1 root disk 94, 2 Jan 16 11:37 dasda2 brw-rw---- 1 root disk 94, 4 Jan 16 11:43 dasdb brw-rw---- 1 root disk 94, 5 Jan 16 11:43 dasdb1 brw-rw---- 1 root disk 94, 6 Jan 16 11:43 dasdb2 dasdb1 in the only one that I can get to mount. When I try to mount dasdb2 I get: [EMAIL PROTECTED] dev]# mount /dev/dasdb2 /mnt/322C mount: you must specify the filesystem type When I try to specify type ext3 I get: [EMAIL PROTECTED] dev]# mount /dev/dasdb2 /mnt/322C -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/dasdb2, or too many mounted file systems Does Centos/RedHat Enterprise 4 use a different filesytem type, and if so, how do I find out what it is? Also, I am curious why df shows the root file system at /dev/mapper/VolGroup00-LogVol00. Thanks for your patience with me, Russ Jones ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
