- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Dealing with stale extents (I/O 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
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
10-25-2006 06:08 AM
10-25-2006 06:08 AM
Dealing with stale extents (I/O error)
I went ahead and broke the mirrors, reduced the bad disk out of the vg, replace, did the pvcreate, vgextend and mkboot commands. I then started to remirror the lvols. Now, I have three lvols (lvol3, lvol7 and lvol8) that are reporting stale extents and wont sync.
What course of action do I have? Tape restore?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2006 06:15 AM
10-25-2006 06:15 AM
Re: Dealing with stale extents (I/O error)
lvsync sometimes helps. If not, you may need to destroy the logical volumes and restore the data form tape.
Sorry.
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
10-25-2006 06:18 AM
10-25-2006 06:18 AM
Re: Dealing with stale extents (I/O error)
echo 2400?20x | adb {device name}
for both disks. Can someone explain the output to me?
This is the output from the drive that had all of its extents current before I broke the mirrors and replaced the "bad" drive.
# echo 2400?20x | adb /dev/dsk/c3t0d0
2400: 4445 4645 4354 3031 0xB0C9 0xF598 8000 0
0xB046 3260 8000 0 0xB0B2 3F60 8000 0
0xB0C6 0xAC60 8000 0
This is the output from the replaced drive and is still reporting stale extents.
# echo 2400?20x | adb /dev/dsk/c2t1d0
2400: 4445 4645 4354 3031 0 0 0 0
0 0 0 0 0 0 0 0
0 0 0 0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2006 06:29 AM
10-25-2006 06:29 AM
Re: Dealing with stale extents (I/O error)
It seems to me that if everything was good on the mirrored drive, then the extents should sync right back up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2006 07:53 AM
10-25-2006 07:53 AM
Re: Dealing with stale extents (I/O error)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2006 11:54 AM
10-25-2006 11:54 AM
Re: Dealing with stale extents (I/O error)
It sounds like a mirroring issue.
flg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2006 12:45 PM
10-25-2006 12:45 PM
Re: Dealing with stale extents (I/O error)
NOTE: Since this is VG00, the replaced disk must be restored with boot information too. This is not accomplished with lvsync because the boot area is not part of an lvol.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2006 01:56 PM
10-25-2006 01:56 PM
Re: Dealing with stale extents (I/O error)
Read my initial post. After replacing the hard drive, I ran pvcreate, vgextend and mkboot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2006 02:06 PM
10-25-2006 02:06 PM
Re: Dealing with stale extents (I/O error)
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2006 02:08 PM
10-25-2006 02:08 PM
Re: Dealing with stale extents (I/O error)
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2006 06:25 PM
10-25-2006 06:25 PM
Re: Dealing with stale extents (I/O error)
As said STALE does not mean it's bad news in most cases but another way to try if a disk is no good, which I use, is the following command - HPUX-
dd if=/dev/rdsk/c?t?d? of=/dev/null bs=1024 count=1
This may take time to complete but it will indicate a failing disk that the ioscan command may not pick up.
hope this helps.
kyris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2006 07:19 PM
10-25-2006 07:19 PM
Re: Dealing with stale extents (I/O error)
Have you tried to take the disk out and put it back, might need a re-spin.
Have you tested the disk, to see it's not a DOA.
What's the exact error you get on the 3 lvols?
- Do you've SCSI errors in your syslog?
- What's the result of pvdisplay/diskinfo?
Darrel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2006 01:06 AM
10-26-2006 01:06 AM
Re: Dealing with stale extents (I/O error)
pvdisplay -v /dev/dsk/c2t1d0|grep stale
00561 stale /dev/vg00/lvol3 00011
01425 stale /dev/vg00/lvol7 00000
01589 stale /dev/vg00/lvol7 00164
01615 stale /dev/vg00/lvol8 00002
01621 stale /dev/vg00/lvol8 00008
The stale extents match up with what I am seeing when I run lvdisplay.
There are no stale extents on the other drive.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2006 01:08 AM
10-26-2006 01:08 AM
Re: Dealing with stale extents (I/O error)
# dd if=/dev/dsk/c2t1d0 of=/dev/null bs=1024 count=1
1+0 records in
1+0 records out
I can run it for he entire disk but it will take up to 2 hours to finish.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2006 01:26 AM
10-26-2006 01:26 AM
Re: Dealing with stale extents (I/O error)
# dd if=/dev/dsk/c2t1d0 of=/dev/null bs=1024
35566480+0 records in
35566480+0 records out
I'll run against other disk as well and report back.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2006 01:43 AM
10-26-2006 01:43 AM
Re: Dealing with stale extents (I/O error)
dd if=/dev/dsk/c2t1d0 of=/dev/null bs=256k
I think you'll find 64k to 512k significantly faster.
Bill Hassell, sysadmin