- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Weired warning
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
Discussions
Discussions
Forums
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
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
тАО11-23-2004 06:19 AM
тАО11-23-2004 06:19 AM
Weired warning
I understand that someone has added these volumes to these disks, but not propagated on other side. What best option someone thinks to wipe this out as VG is not active on adoptive node, and i want both sides to be in synx.
Thanks a lot-------Prashant
Warning: Logical Volume number "183" found on physical volume not found in "/tmp/vgECPRD3.map".
Warning: Logical Volume number "184" found on physical volume not found in "/tmp/vgECPRD3.map".
Warning: Logical Volume number "185" found on physical volume not found in "/tmp/vgECPRD3.map".
Warning: Logical Volume number "186" found on physical volume not found in "/tmp/vgECPRD3.map".
Warning: A backup of this volume group may not exist on this machine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2004 06:24 AM
тАО11-23-2004 06:24 AM
Re: Weired warning
You can create the device files manually on the adoptive node using mknod.
Make sure you create the character as well as the block device and they have the same major/minor number and the same names as they are on the primary node.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2004 06:24 AM
тАО11-23-2004 06:24 AM
Re: Weired warning
Thnx
Prashant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2004 06:27 AM
тАО11-23-2004 06:27 AM
Re: Weired warning
lvremove is the only way. But for that to work, the vg should be active on the node.
If you delete the device files and leave it like that, doing a pvdisplay -v /dev/dsk/cxtydz would show you extents with "???" in place of the lv name.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2004 04:25 PM
тАО11-23-2004 04:25 PM
Re: Weired warning
Well I would get a fresh map file from the primary side and just redo the procedure. Then it will know of the new lvols and their respective names.
Regards
Gerhard