Operating System - HP-UX
1753874 Members
7467 Online
108809 Solutions
New Discussion юеВ

fsck with invalid device config entry found

 
SOLVED
Go to solution
emily_3
Frequent Advisor

fsck with invalid device config entry found

I tried to change lvol12 to larger fs.

# fsadm -o largefiles /dev/vg00/rlvol12
vxfs fsadm: file system dirty, run fsck first

So I did # fsck -y -F vxfs -o full /dev/vg00/rlvol12
vxfs fsck: invalid device config entry found
log replay in progress

Can someone tell me how to slove this problem?
Thanks.
10 REPLIES 10
Michael Steele_2
Honored Contributor

Re: fsck with invalid device config entry found

emily_3
Frequent Advisor

Re: fsck with invalid device config entry found

I tried the following command, and seems the same result.

# fsck -F vxfs -V -y -o full /dev/vg00/rlvol12
fsck -F vxfs -y -o full /dev/vg00/rlvol12

# fsck -F vxfs -y -o full /dev/vg00/rlvol12
vxfs fsck: invalid device config entry found
log replay in progress


Norman_21
Honored Contributor
Solution

Re: fsck with invalid device config entry found

Emily,

Try this, and if it didn't work then you might need the latest vxfs/fsck
patches to be installed:

fsck -F vxfs -o full,nolog -y /dev/vg00/lvol12


In fact when you reboot your sever, fsck will run automatically to check and fix the filesystems, in some cases, it might prompt you for an action!

Good luck
"Attitudes are contagious, is yours worth catching"/ My first point was given by SEP on January 31, 2003
emily_3
Frequent Advisor

Re: fsck with invalid device config entry found


It does work! Thanks.
But I would like to know what's the meaning of "nolog"?
And where could I find the option information:
#fsck -o "option"
Norman_21
Honored Contributor

Re: fsck with invalid device config entry found

Emily,

Since I don't have fsadm installed in my server so I would advise you to unmoun the file system prior to running fsck.
Here are the options:

-F file system type
-n assumes a NO answer for fsck questions
-y assumes a YES answer for fsck questions
-b this is for hfs filesystems only which tells fsck to use superblock, look at the file /var/adm/sbtab.
-f forces fsck to run on a mounted file system(HFS only)
-o full Forces fsck to make a full check of the metadata instead of just replying the intent log(JFS only)
-o nolog Prevents intent log reply (JFS only)

Also, all above options can be found on the man page
# man fsck

Please consider assinging points.
"Attitudes are contagious, is yours worth catching"/ My first point was given by SEP on January 31, 2003
emily_3
Frequent Advisor

Re: fsck with invalid device config entry found


I know use "#man fsck" to see all the option, but I didn't find the suboption under -o. here is the description of the "-o"
Do you know where could I find the file-system-specific manual? Thanks.

-o FSspecific-options
Specify options specific to each file system type.FSspecific-options is a list of suboptions and/or keyword/attribute pairs intended for a file-system-specific version of the command. See the file-system-specific manual entries for a description of the specific_options supported, if any.
Norman_21
Honored Contributor

Re: fsck with invalid device config entry found

-F vxfs (for JFS filesystems)
-F hfs (for HFS filesystems)

Although, you didn't mention what version are you running, but for 10.20 and higher
the /stand file system is the only HFS file system, others are vxfs file systems.
# mount -v (will tell you what type of file systems you have).

Take care and good luck
"Attitudes are contagious, is yours worth catching"/ My first point was given by SEP on January 31, 2003
T G Manikandan
Honored Contributor

Re: fsck with invalid device config entry found

man fsck_vxfs
Norman_21
Honored Contributor

Re: fsck with invalid device config entry found

and man fsck_hfs for hfs file systems!
"Attitudes are contagious, is yours worth catching"/ My first point was given by SEP on January 31, 2003