- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- fsck 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
11-19-2007 01:20 AM
11-19-2007 01:20 AM
fsck error
while running fsck for a vxfs file system following error is displayed
# fsck -F vxfs -o full -y /dev/vgxx/rlvolname
1)vxfs fsck : filesystem had a i/o errors on userdata
2)log replay in progress
3)pass0-checking structral files.
4)pass1-checking inode sanity and blocks
5)fileset 999 primary inode 2 marked bad,allocation flags (0x0001)
6)file set 999 primary inode 2 failed validation clear? (YNQ)Y
7)root inode for file set 999 is invalid
8)full file system check required, exiting....
if i give NO option in point 6 it is going inside for inode checking for about 45000 inodes asking for confirmation check for each and every inode, to give YES/NO option is something which is very tedious job. plse help me to solve this.
regards
venkatesan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2007 01:35 AM
11-19-2007 01:35 AM
Re: fsck error
Seems like FSCK is unable to correct the FS corruption !!.
see if you can run fsck with nolog ..
fsck -F vxfs -o full,nolog -y /dev/vgxx/rlvolname
what is the OS version/Vxfs layout
run fstyp .....
fstyp -v /dev/vgxx/rlvol...
Regards,
RD
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2007 01:49 PM
11-19-2007 01:49 PM
Re: fsck error
The OS version is HP Unix B11.00
#fstyp -v /dev/vgxx/rlvolname output is following
vxfs
version:3
f_bsize:8192
f_frsize:8192
f_blocks:5120000
f_bfree:883784
f_bavail:883784
f_files:45600
f_ffree:1073761352
f_favail:1073761352
f_fsid:1074200577
f_basetype:vxfs
f_namemax:254
f_magic:a501fcf5
f_featurebits:0
f_flag:0
f_fsindex:6
f_size:5120000
Pls see and reply for this ..
regards,
Venkatesan.G
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2007 02:05 PM
11-19-2007 02:05 PM
Re: fsck error
Please install the latest fsck patch
PHCO_23651 11.00 fsck_vxfs(1M) cumulative patch
a few known issue:=
PHCO_23651: CORRUPTION
A significantly fragmented VxFS filesystem may
be corrupted by fsck_vxfs(1M). Two consecutive
invocations of fsck_vxfs(1M) can result in a
directory corruption.
WK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2007 12:51 AM
11-21-2007 12:51 AM
Re: fsck error
I have downloaded and installed the patch PHCO_23651 and depended patches. after installing it is asking for kernal rebuilding at the end, task is suspended due to following errors found in the log file.
note: building a new kernel based on template file "/stand/system" generating module: krm.....
/usr/bin/mkdir -p /stand/build
loading kernel
ld: unsatisfied symbol "mlock_valid_args" in file /usr/conf/lib/libhp_ux.a [vm_clic.o]
ld: unsatisfied symbol "prf_klog_getmount" in file /usr/conf/lib/libhp_ux.a [klog.o]
ld: unsatisfied symbol "prf_klog_getstring" in the file /usr/conf/lib/libhp_ux.a [klog.o]
ld: unsatisfied symbol "pwrite" in the file /usr/conf/lib/libhp_ux.a [scall_stubs.o]
ld: unsatisfied symbol "lock_claim" in file /usr/conf/lib/liblvm.a [lv_hp.o]
ld: unsatisfied symbol "set_timeout" in the file /usr/conf/lib/libhp_ux.a [safety_time.o]
ld: unsatisfied symbol "pread" in the file /usr/conf/lib/libhp_ux.a [scall_stubs.o]
ld: unsatisfied symbol "lock_disown" in file /usr/conf/lib/liblvm.a [lv_hp.o]
8 errors
**** error exit code 1
stop
make faliure
error: the command "usr/sbin/mk_kernel, which is used to rebuild the kernel, has failed. becoz kernel related filesets were installed. this command must be executed by "swinstall"
without failures, before the load can continue. check the above output for the failure.
note : the installed phase has suspended. check above out put for reason.
please give your inputs to resolve this.
thanks & regards
venkatesan.G
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2007 07:08 PM
11-21-2007 07:08 PM
Re: fsck error
run check_patches to see what kind of errors you face.
i suspected your reinstall PHKL_18543, this will cause kernel unable to regen.
check this doc of how to recover it
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c01005576-2
WK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2007 11:27 PM
11-21-2007 11:27 PM
Re: fsck error
i ran the command #check_patches it is giving the some report.same file attached for reference.pls see that report reply to resolve the issue.
thanks & regards,
Venkatesan.G