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 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Tuesday, January 16, 2007 6:17 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR Whatever the partition number on the source volume, will be the partition number on the target volume. So, if your root partition is /dev/dasda2 on the source, then in your case the root partition will be /dev/dasdb2 on the system where you are modifying it. If it was /dev/dasda3, then use /dev/dasdb3. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Russell Sent: Tuesday, January 16, 2007 5:01 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR I have been working through the HowTo on Cloning Red Hat Linux. I copied my Linux dasd volume using MVS. I brought the new volume online, and it showed up as dasdb. When I mount /dev/dasdb1, I seems to be mounting the boot partition and not the root file system. Any suggestions would be appreciated. Thanks, 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
Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR
Could the /dev/dasdb2 filesystem have been an LVM volume group? /dev/mapper/VolGroup00-LogVol00 would be the type of things you might see for LVM volumes. My system shows the following in df (truncated because I love loop-back mounts...) rockhopper:~ # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/system-rockhopper 8589044 7863536725508 92% / tmpfs 405156 4405152 1% /dev/shm /dev/dasda1 86380 14756 67168 19% /boot /dev/mapper/vg_iso-lv_media 27355500 25573528 1504100 95% /iso /dev/mapper/vg_local-lv_ibmitm 6713132220156 6492976 4% /opt/IBM/ITM /dev/dasda1 is my /boot, and everything else are LVM volumes. Try the command pvdisplay /dev/dasdb2 to see if it is a physical volume that was part of a volume group. If it was, then possibly try vgscan to see if it finds /dev/dasdb2 as part of a volume group. The big problem might come if the volume group has the same name as the one on the system you've attached it to -- .~.Robert P. Nix Mayo Foundation /V\RO-OC-1-13 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. From: Jones, Russell [EMAIL PROTECTED] Reply-To: Linux on 390 Port LINUX-390@VM.MARIST.EDU Date: Wed, 17 Jan 2007 08:39:47 -0600 To: LINUX-390@VM.MARIST.EDU Conversation: New HOWTO: Cloning Red Hat Linux Running in an LPAR 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 -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Tuesday, January 16, 2007 6:17 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR Whatever the partition number on the source volume, will be the partition number on the target volume. So, if your root partition is /dev/dasda2 on the source, then in your case the root partition will be /dev/dasdb2 on the system where you are modifying it. If it was /dev/dasda3, then use /dev/dasdb3. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Russell Sent: Tuesday, January 16, 2007 5:01 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR I have been working through the HowTo on Cloning Red Hat Linux. I copied my Linux dasd volume using MVS. I brought the new volume online, and it showed up as dasdb. When I mount /dev/dasdb1, I seems to be mounting the boot partition and not the root file system. Any suggestions would be appreciated. Thanks, 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 -- 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
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
Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR
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
Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR
So, it looks like you copied the disk from aplnx02 itself, and now you're trying to mount the copy on aplnx02. That's probably not going to work particularly well. The problem isn't the volume group name so much as the UUID that gets written to the physical volume (PV) during the pvcreate. Trying to get around this could get rather complex. If you're up for that, email me off-list, and I'll try to work through it with you. Once we get things working (or give up), we can post what happened back to the list. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Russell Sent: Wednesday, January 17, 2007 12:29 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR 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 -- 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
Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR
Two possible options, as far as I can tell: vgrename will let you change the name of a volume group... But you might have to change the name of the volume group on your running system; I'm not sure it would let you change the one on the unmounted pack. vgsplit will let you split off some of the physical volumnes in a volume group. You might be able to split the only volume into a different volume group name. I noticed that the pv identifiers for /dasda2 and /dasdb2 are identical. Was dasdb a copy of dasda? Having these pv identifiers being equal may be an issue that would keep you from getting them both up on the same running system. LVM identifies the physical volumes by these identifiers, so when the system comes up with both these disks available, LVM would not be able to identify the pv that truly should be part of the running system¹s volume group. Using ³vgexport² and then ³vgimport² on the volume might help matters, but I¹m not sure as I haven¹t really been there Of course, as with all such experiements, be sure to have a good backup of /dev/dasdb (and /dev/dasda, for that matter) before attempting any sort of recovery, as you cannot be sure if any such attempt might prove to be destructive Have you thought about trying to bring up dasdb by itself in the LPAR, or in a separate LPAR? It might come up to a point where you could work with the data. -- .~.Robert P. Nix Mayo Foundation /V\RO-OC-1-13 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. From: Jones, Russell [EMAIL PROTECTED] Reply-To: Linux on 390 Port LINUX-390@VM.MARIST.EDU Date: Wed, 17 Jan 2007 11:28:45 -0600 To: LINUX-390@VM.MARIST.EDU Conversation: New HOWTO: Cloning Red Hat Linux Running in an LPAR Subject: Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR Results from the scan commands: [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? -- 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
Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR
I have been working through the HowTo on Cloning Red Hat Linux. I copied my Linux dasd volume using MVS. I brought the new volume online, and it showed up as dasdb. When I mount /dev/dasdb1, I seems to be mounting the boot partition and not the root file system. Any suggestions would be appreciated. Thanks, Russ Jones -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Monday, January 15, 2007 9:21 AM To: LINUX-390@VM.MARIST.EDU Subject: New HOWTO: Cloning Red Hat Linux Running in an LPAR A new HOWTO has been added to the web site: Cloning Red Hat Linux Running in an LPAR. A couple of people had expressed interest in seeing Mike's original document, so I made myself take the time over the weekend to get it formatted. Thanks to Mike Nettles, for documenting his methods for the rest of us. http://linuxvm.org/info/HOWTOs/ 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 -- 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
Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR
Whatever the partition number on the source volume, will be the partition number on the target volume. So, if your root partition is /dev/dasda2 on the source, then in your case the root partition will be /dev/dasdb2 on the system where you are modifying it. If it was /dev/dasda3, then use /dev/dasdb3. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jones, Russell Sent: Tuesday, January 16, 2007 5:01 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: New HOWTO: Cloning Red Hat Linux Running in an LPAR I have been working through the HowTo on Cloning Red Hat Linux. I copied my Linux dasd volume using MVS. I brought the new volume online, and it showed up as dasdb. When I mount /dev/dasdb1, I seems to be mounting the boot partition and not the root file system. Any suggestions would be appreciated. Thanks, 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
