![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| HP-UX HP-UX (Hewlett Packard UniX) is Hewlett-Packard's proprietary implementation of the Unix operating system, based on System V. |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Data Recovery from file system overwritten with LVM. | squid04 | UNIX for Advanced & Expert Users | 2 | 10-01-2008 03:22 AM |
| how to verify that copied data to remote system is identical with local data. | ynilesh | Shell Programming and Scripting | 3 | 01-31-2008 05:55 AM |
| Shell Script --- Delete ORA error from data file | sk005 | UNIX for Dummies Questions & Answers | 1 | 09-25-2007 02:26 PM |
| Error: Internal system error: Unable to initialize standard output file | firkus | UNIX for Dummies Questions & Answers | 2 | 10-25-2005 12:23 PM |
| Meta Devices | ozzmosiz | SUN Solaris | 8 | 05-16-2005 08:43 PM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
file system had I/O error(s) on meta-data
I'm having this error when I do full fs cleanup
# fsck -F vxfs -o full /dev/vg01/lvol1 vxfs fsck: file system had I/O error(s) on meta-data. log replay in progress vxfs fsck: file system had I/O error(s) on meta-data. vxfs fsck: file system had I/O error(s) on meta-data. pass0 - checking structural files pass1 - checking inode sanity and blocks vxfs fsck: fsck read failure bno = 1616, off = 0, len = 8192 I looked in /sbin/dmesg, it gives me this error below, so does in /var/adm/syslog/syslog.log file(although in there it gives more 123, 124, etc inode issues) vxfs: mesg 016: vx_ilisterr - /xxxxx file system error reading inode 122 it doesn't report any disk failure except on inode failures#...I did run fsck on those fs in question I had. Still reports this inode problem. Want to know if this harware call? |
| Forum Sponsor | ||
|
|
|
#2
|
||||
|
||||
|
You need to look at the hardware logs to see if this is a hardware issue or not. It could be just a file system that got scribbled on somehow. The documentation is here: http://docs.hp.com/en/diag.html Start with the Support Tools overview.
|
|
#3
|
|||
|
|||
|
Got it
You are right, it's not the hardware call, have to endup doing restore after recreating fs. Good site. Thanks.
|
|||
| Google The UNIX and Linux Forums |