Operating System - HP-UX
1753810 Members
8102 Online
108805 Solutions
New Discussion юеВ

Re: scripting vgimport commands - bad results?

 
paul cummings
Advisor

Re: scripting vgimport commands - bad results?

Brian - re: environments being different when running the script... Note that I do not specify the full path of the vgimport/vgexport commands, but of the mapfile to be imported/exported. i.e. run in /

If you see my original note, you'll see the mapfiles are being saved as:

/vgdb2_mapfile_orig

and so on.

Pete Randall
Outstanding Contributor

Re: scripting vgimport commands - bad results?

My apologies to JRF, but the -s option (by itself, without the -p option) WILL most definitely remove the volume group and its underlying structures from the exporting system.

Been there, done that - on purpose, thankfully.

Pete

Pete
James R. Ferguson
Acclaimed Contributor

Re: scripting vgimport commands - bad results?

Hi Pete:

No apology necessary. You are absolutely correct. Without the '-p' the 'vgexport -s' will indeed remove the vg definitions from the exporting system. I'm note sure what I was thinking. Thanks.

Regards!

...JRF...
paul cummings
Advisor

Re: scripting vgimport commands - bad results?

But in my case, I do want to remove the entry from lvmtab, because the vg is getting renamed in the process and c?t?d? devices are being re-used as different VG names - so I can't have device conflicts in the file. so in this case, i will not use the -p option.

thanx!
-paul
Darrell Allen
Honored Contributor

Re: scripting vgimport commands - bad results?

Hi Paul,

Is it working for you now? I'm sorry for asking but I couldn't quite gather if you've determined anything yet.

Darrell
"What, Me Worry?" - Alfred E. Neuman (Mad Magazine)