- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- file system corrupt
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-04-2007 03:50 AM
тАО06-04-2007 03:50 AM
# mount /t230817
vxfs mount: /dev/vg02/lvt230817 is corrupted. needs checking
# fsck -F vxfs -y /dev/vg02/lvt230817
vxfs fsck: file system had I/O error(s) on meta-data.
vxfs fsck: file system had I/O error(s) on user data.
log replay in progress
pass0 - checking structural files
pass1 - checking inode sanity and blocks
vxfs fsck: fsck read failure bno = 5259664, off = 0, len = 8192
file system check failure, aborting ...
# echo $?
1
#
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 04:00 AM
тАО06-04-2007 04:00 AM
Re: file system corrupt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 04:14 AM
тАО06-04-2007 04:14 AM
Re: file system corrupt
# lvdisplay /dev/vg02/lvt230817
lvdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t10d0":
The specified path does not correspond to physical volume attached to
this volume group
lvdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg02/lvt230817
VG Name /dev/vg02
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 22000
Current LE 2750
Allocated PE 2750
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default
# ioscan -fnCdisk
lClass I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 8/4.5.0 sdisk CLAIMED DEVICE SEAGATE ST34573WC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/4.8.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
disk 2 8/4.9.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c0t9d0 /dev/rdsk/c0t9d0
disk 3 8/4.10.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c0t10d0 /dev/rdsk/c0t10d0
disk 4 8/4.11.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c0t11d0 /dev/rdsk/c0t11d0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 04:25 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 04:54 AM
тАО06-04-2007 04:54 AM
Re: file system corrupt
> vxfs fsck: file system had I/O error(s) on meta-data.
> vxfs fsck: file system had I/O error(s) on user data.
fsck cannot fix bad spots on the disk so the disk must be replaced and then reloaded from backup. fsck fixes logical errors in the directories but cannot fix any hardware problems. If this data is invaluable, contact a disk recovery company like OnTrack or DriveSavers. Make sure they know something about HP-UX. NOTE: expect to pay several thousand $$$ to recover the data.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 04:29 PM
тАО06-04-2007 04:29 PM
Re: file system corrupt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2007 05:54 PM
тАО06-04-2007 05:54 PM
Re: file system corrupt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-05-2007 02:58 AM
тАО06-05-2007 02:58 AM
Re: file system corrupt
# lvdisplay /dev/vg02/lvt230817
lvdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t10d0":
The specified path does not correspond to physical volume attached to
this volume group
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-05-2007 03:08 AM
тАО06-05-2007 03:08 AM