- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Unique PVID's error message
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
тАО06-01-2009 05:55 AM
тАО06-01-2009 05:55 AM
Syslog-check on oc1 is WARNING: (1): May 30 04:00:30 oc1 LVM[1228]: Unique PVID: The contents of the file /etc/lvmconf/pv_lock were overwritten with same data or the file time stamp on the file was modified. Possibly touch(1M) or tar -x operation was performed on the file. There could be delay or failure in the generation of unique PVIDs.
Thanks in advance,
/KPS
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2009 06:28 AM
тАО06-01-2009 06:28 AM
SolutionThe 'pv_lock' file is used by 'pvcreate'. It should not be modified manutally. It is used to insure that at least one-second elapses between sucessive 'pvcreate' operations. This insures that the PVID written to an LVM physcial disk is unique, since the PVID consists of an Epoch seconds component and the unique machine ID as seen in 'uname -i'.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2009 06:36 AM
тАО06-01-2009 06:36 AM
Re: Unique PVID's error message
This is a common occurrence in SG clusters where the unique id is written by one system on shared storage and detected as an issue on the second node.
This data can not be manually manipulated and I think you are just going to have to live with it.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2009 06:48 AM
тАО06-01-2009 06:48 AM
Re: Unique PVID's error message
This particular HP-UX 11.23 host that we have been using DRD with is not a clustered host.
It sounds like that we are seeing this because when we use DRD, it's using "pvcreate" to initialize the spare disk we're using for this and as a result it needs to use the uniqe PVID? This is good info and we can live with it, I just wanted to make sure it wasn't a serious issue that needed immediate action.
Many Thanks,
/KPS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2009 06:49 AM
тАО06-01-2009 06:49 AM