- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Veritas VxVM Disk Issue
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
тАО03-10-2008 05:59 AM
тАО03-10-2008 05:59 AM
Is there something within Veritas that needs to be addressed ?
I can re-initialize the disk and put it back into service and not have any issues...
Failures have been detected by the VERITAS Volume Manager:
failed disks: ignitedg04
failed plexes: sourceslv-01
The Volume Manager will attempt to find spare disks, relocate failed subdisks and then recover the data in the failed plexes.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2008 06:35 AM
тАО03-10-2008 06:35 AM
Solutioncould you give us a bit more info, like are these internal disks or luns from a san/nas etc.
Could you test the disk with dd.
# vxdisk list
find the device file of the affected disk
# dd if=/dev/rdsk/cxtydz of=/dev/null bs=1024k
watch your dmesg/syslog.log for errors.
Regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2008 06:56 AM
тАО03-10-2008 06:56 AM
Re: Veritas VxVM Disk Issue
http://seer.entsupport.symantec.com/docs/184960.htm
A small i/o timeout in the LUN can cause the flag of the disk to be set as failed.Confirm there was no scsi i/o time outs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2008 07:26 AM
тАО03-10-2008 07:26 AM
Re: Veritas VxVM Disk Issue
With vxvm always provide the following info.
#vxdisk -o alldgs list
(cut&paste relevant info)
#vxprint -ht
(cut&paste relevant info)
In youre case, I suppose the above message is logged to the root mailbox, check the timestamp of the message and check if any relevant scsi/vxvm messages are logged around this time in the (OLD)syslog.log.
Best Regards,
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2008 09:14 AM
тАО03-10-2008 09:14 AM
Re: Veritas VxVM Disk Issue
With the release of VERITAS Volume Manager 3.5, 128 Kbytes of disk space in the beginning of a disk are reserved for the cross-platform data sharing feature. As the result of this, the public region length (usable length of the disk device) is miscalculated, and Volume Manager may create subdisks that extend beyond the end of the underlying physical disk, possibly compromising data availability.
Disks need to be re-initialized AFTER Update3 or 4 patches have been installed...
1. Make sure the one of the following patches has been installed:
PHKL_30756 or 33356 or 34254 or 35292 or 25816 or 36529 or 36995
If not, you might want to download and install PHKL_36995 and dependencies patches from itrc.hp.com. A reboot is required after patch installation.
2. Then you can re-initialize Disks effected...