Sponsored Content
Operating Systems HP-UX fsck! How to run Full File System Check Post 302135663 by hungevntelecom on Tuesday 11th of September 2007 12:41:36 PM
Old 09-11-2007
fsck! How to run Full File System Check

Dear all

I am new for HP-UX.
I have HP rp2470 running HP-UX 10.x
When i run fsck in a root, the output is as below:

Code:
#:root> fsck
fsck: /dev/vg00/rlvol1: mounted file system

continue (y/n)? y
** /dev/vg00/rlvol1
** Last Mounted on /stand
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
45 files, 0 icont, 38040 used, 45693 free (77 frags, 5702 blocks)
vxfs fsck: /dev/vg00/lvol3 is currently mounted
vxfs fsck: /dev/vg00/lvol4 is currently mounted
vxfs fsck: /dev/vg00/lvol6 is currently mounted
vxfs fsck: /dev/vg00/lvol7 is currently mounted
vxfs fsck: file system had I/O error(s) on meta-data.
log replay in progress
full file system check required, exiting ...
vxfs fsck: /dev/vg00/lvol5 is currently mounted


Then if i run fsck -y, the output as below:

Code:
#:root> fsck -y
fsck: /dev/vg00/rlvol1: mounted file system
vxfs fsck: /dev/vg00/lvol3 is currently mounted
vxfs fsck: /dev/vg00/lvol4 is currently mounted
vxfs fsck: /dev/vg00/lvol6 is currently mounted
vxfs fsck: /dev/vg00/lvol7 is currently mounted
vxfs fsck: file system had I/O error(s) on meta-data.
log replay in progress
pass0 - checking structural files
pass1 - checking inode sanity and blocks
vxfs fsck: fsck read failure bno = 1566, off = 0, len = 8192
file system check failure, aborting ...
vxfs fsck: /dev/vg00/lvol5 is currently mounted

Plz help me explain these output and tell me How to run a full file system check to correct this I/O error(s) on meta-data as above.

Thanks for your support

Last edited by Yogesh Sawant; 04-10-2011 at 11:06 AM.. Reason: added code tags
 

9 More Discussions You Might Find Interesting

1. Solaris

File system full?

Hi, I just started working with UNIX on an old semi-fossilized Sun workstation which I use to process LOTS of images,however, I just started to get an error message that the file system is full and then my shell tool or/and text editor freeze up. Help? (8 Replies)
Discussion started by: Bend
8 Replies

2. UNIX for Dummies Questions & Answers

File System Check (fsck)

I am having a problem with fsck. I am new to UNIX but was placed in a position where I must learn it. Anyway, one of the instructions that I have been given is to use 'fsck -f -y' when I am having trouble with the filesystem. The problem is that I am getting an error message that says the -f... (1 Reply)
Discussion started by: mawalton
1 Replies

3. UNIX for Dummies Questions & Answers

fsck on a mounted file system?

I have a Solaris 7 box. We got a strange error in the syslog, which read as follows: Nov 15 11:50:16 server-01 unix: NOTICE: free inode /mount1/8025691 had size 0x20d I consulted with a fellow sysadmin, and he suggested running "fsck -N" on the filesystem in question without unmounting it. So I... (1 Reply)
Discussion started by: GKnight
1 Replies

4. Solaris

fsck run

Hi, Can anybody tell me that is it the command "fsck" can be run by the root account only? Thanks. (2 Replies)
Discussion started by: efang
2 Replies

5. Solaris

FSCK root file system (/dev/vx/dsk/bootdg/rootvol)

Hi, I need to fsck the root file system on my Solaris 9 server. It is a UFS file system but it is under Veritas control. I want to know which fsck I need to use to check the file system. The default Solaris fsck (/usr/sbin/fsck) or the Veritas (/lib/fs/vxfs/sparcv9/fsck) fsck? I take it I... (3 Replies)
Discussion started by: gwhelan
3 Replies

6. UNIX for Dummies Questions & Answers

Run fsck on root file system

If i run fsck on one filesystem and fsck need to repair some things then this partition must be unmounted correct ? So running fsck on root file system isn't possible within same OS ? correct ? What is the best way to do that, live cd ? BR, Jurif (5 Replies)
Discussion started by: jurif
5 Replies

7. Red Hat

File system full, but not really.

Hey all, What do you think mostly happened in the following situation? I have a Red Hat 5.5 server. Someone, somehow, managed to get two .nfs000.... type files that totaled over a terabyte in size. I removed them and thought things were back to normal. Then I started getting complains from... (2 Replies)
Discussion started by: geelsu
2 Replies

8. Solaris

Not able to run fsck on root file system

I am trying to root disk mirroring on SunFire V210 Server. There are two disks on this server c1t0d0 and c1t1d0 . I completed all the steps and I updated the vfstab file too. After I have updated the vfstab file I run df -h command but could not see the changes i made in vfstab. Suddenly the server... (1 Reply)
Discussion started by: newbi8321
1 Replies

9. Solaris

unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0)

What can I fix this issue? I have ran below commands but everything is same.:confused: WARNING: Last shutdown is later than time on time-of-day chip: check date. The / file system (/dev/rdsk/c1t0d0s0) is being checked WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 Replies
FSCK(1) 						      General Commands Manual							   FSCK(1)

NAME
fsck, fsck1 - perform file system consistency check SYNOPSIS
fsck [-aclmrs] [device] ... OPTIONS
-a Automatically repair inconsistencies -c Check and list only the specified i-nodes -l List the files and directories in the filesytem -r Prompt user for repairs if inconsistencies are found -s List the superblock of the file system EXAMPLES
fsck /dev/hd4 # Check file system on /dev/hd4 fsck -a /dev/at0 # Automatically fix errors on /dev/at0 fsck -l /dev/fd0 # List the contents of /dev/fd0 fsck -c 2 3 /dev/hd3 # Check and list /dev/hd3 i-nodes 2 & 3 DESCRIPTION
Fsck performs consistency checks on the file systems which reside on the specified devices. Fsck1 is an alternate version for use on obso- lete V1 file systems. When either the -a or -r flags are given, the file system will be repaired if errors are found. Before running fsck on a mounted file system, it must first be unmounted. Trying to repair a mounted file system is dangerous and should not be attempted. To repair the root file system (which cannot be unmounted), first type CTRL-F9 at the console to kill any and all processes. Log back in as root, type sync to force any buffered changes to disk, run fsck on the root file system and immediately reboot the computer by typing reboot. It is necessary to kill all processes before repairing the root file system to prevent them from modifying any disk blocks while fsck is running. This is only necessary for the root file system, any other file system can simply be unmounted before it is checked. SEE ALSO
mkfs(1), mount(1). FSCK(1)
All times are GMT -4. The time now is 10:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy