Oooo, I had this problem... Now how did I fix it? Hmmm. Sounds like you're stuck tonight.. So I'll give you what I think I remember I did, with a caveat that many brain cells may have replaced those since then.
Pvscan showed the volumes still there. That was good. PV didn't seem to care about the new name. And then I ended up vgexporting the volume group and then vgimporting it again. Make sure you have done enough mknod to cover all your volumes. Marcy Cortes Enterprise Hosting Services - z/VM and z/Linux (415) 243-6343 "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rob Schwartz Sent: Thursday, October 19, 2006 8:29 PM To: [email protected] Subject: Re: [LINUX-390] vgcfgrestore -o Hey Mark... Tried that... Works on some PVs but not all in the VG... The message is vgcfgrestore -- "/dev/dasdu1" may not be an actual physical volume of volume group "vgdata" So now I have a real mess.... Thank you! Rob ----- Original Message ----- From: "Post, Mark K" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, October 19, 2006 11:22 PM Subject: Re: vgcfgrestore -o Rob, You might need to use this: -o, --oldpath OldPhysicalVolumePath If the path to the physical volume has changed between backup time and restore time, this option enables you to choose the corresponding physical volume path in the backup file. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rob Schwartz Sent: Thursday, October 19, 2006 10:20 PM To: [email protected] Subject: vgcfgrestore -o Hey everyone, I'm having some difficulties... kernel 2.4.19 and lvm 3.0.6. I'm trying to restore a vg config . On the cfg backup the original pv was /dev/dasdt1 (PV UUID last digits KgtiDw). The current pv is /dev/dasdu1 and I mucked up the VGDA on that PV so that it has another PV UUID). Now I'm trying to fix it... vgcfgrestore -f /etc/lvmconf/vgdata.conf.1.old --name vgdata -o /dev/dasdt1 -v /dev/dasdu1 says vgcfgrestore -- "/dev/dasdu1" may not be an actual physical volume of volume group "vgdata" Why can't I get LVM to just write the /dev/dasdt1 backup onto the /dev/dasdu1 VGDA?? Thanks, Rob ---------------------------------------------------------------------- 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
