- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: vgimport error
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2000 12:52 AM
04-05-2000 12:52 AM
vgimport error
I have two system in service guard with a AutoRaid
mass storage.
I have configured other 3 LUN and the system created 3 new physical volume
(/dev/dsk/xxxxx) where I created 3 new filesystem.
After this I did this command:
system1: #vgexport -p -s -v MAPFILE /dev/dsk/vgxxx
transferred MAPFILE into system2
system2: recreated the vgxxx
system2: #vgimport -s -m MAPFILE /dev/vgxxx
After this
vgimport: Physical volume "/dev/dsk/cxtxdx" is not a block special file.
....
....
....
Why???
Many Thanks in advances.
Paolo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2000 01:29 AM
04-05-2000 01:29 AM
Re: vgimport error
Looks backwards should be
vgexport -p -s -m MAPFILE /dev/vg##
vgimport -s -m MAPFILE /dev/vg## /dev/dsk/c#t#d#
Mitch
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2000 01:48 AM
04-06-2000 01:48 AM
Re: vgimport error
system and the disks.
Run "ioscan -fnC disk" to verify the disks are there and run "#insf -e" to have
the device special files
installed. I believe you have to name the disks after
the vgimport command if they are seen on different hardware paths from that of
the first system.
vgimport -m MAPFILE /dev/vg?? /dev/dsk/c?t?d? ....
Good Luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2000 09:02 PM
06-06-2000 09:02 PM
Re: vgimport error
On export the "-s" option places the VGID header into the mapfile. When importing the "-s" option causes the import command to search all physical volume headers to find devices matching the VGID listed in the mapfile. Once found it automatically imports them. This is very beneficial when you have multiple disks. This option is not recommended however when using "EMC".
Hope this helps,
Bernie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2000 06:28 AM
06-07-2000 06:28 AM
Re: vgimport error
You will need to recreate your disk device files (using insf) after ioscan returns your devices in the expected order. You may, however, want to check your cabling and ensure that you have the autoraid connected identically to each machine. This is not an absolute requirement, but it will make your life easier.