Home > hp-ux > vxfs extendfs: Invocation of the fsck program terminated abnormally

vxfs extendfs: Invocation of the fsck program terminated abnormally

You will see this message in case you interrupt the extendfs command. I my case I passed block device as an argument to the extendfs command and waited for several minutes (usually it takes one or two) then I remembered that the command expects character device. I read some opinions in Internet and some of them were really horrifying, like: “Well, when you passed block device to extendfs you have to format it and  restore the filesystem from backup“.

Yes, it was stupid to press Ctrl-C, but when people panic they don’t think normally.
root@host:/# extendfs -F vxfs /dev/vg00/lvora

vxfs extendfs: Invocation of the fsck program terminated abnormally.
The file system is marked bad.  Run full fsck manually.
(e.g. fsck -F vxfs /dev/vg00/lvora)

Next step was to make a normal filesystem check:
root@host:/# fsck /dev/vg00/lvora
log replay in progress
log replay failed to clean file system
file system is not clean, full fsck required
full file system check required, exiting …

Mount also says that the filesystem is corrupted:
root@host:/# mount /oracle

vxfs mount: /dev/vg00/lvora is corrupted. needs checking

After reading some manuals and opinions I saw that in this version of HP-UX it doesn”t matter what device is passed because extendfs accepts both. Luckily fsck fixes the problem:
root@host:/root# fsck -y -F vxfs /dev/vgora/lvtest
log replay in progress
log replay failed to clean file system
file system is not clean, full fsck required
pass0 – checking structural files
pass1 – checking inode sanity and blocks
pass2 – checking directory linkage
pass3 – checking reference counts
pass4 – checking resource maps
au 0 summary incorrect – fix? (ynq)y
au 1 summary incorrect – fix? (ynq)y
au 2 summary incorrect – fix? (ynq)y
au 3 summary incorrect – fix? (ynq)y
au 4 summary incorrect – fix? (ynq)y
au 5 summary incorrect – fix? (ynq)y
………………….
au 3500 summary incorrect – fix? (ynq)y
au 3501 summary incorrect – fix? (ynq)y
au 3502 summary incorrect – fix? (ynq)y
au 3503 summary incorrect – fix? (ynq)y
au 3504 summary incorrect – fix? (ynq)y
au 3505 emap incorrect – fix? (ynq)y
au 3505 summary incorrect – fix? (ynq)y
au 3506 emap incorrect – fix? (ynq)y
au 3506 summary incorrect – fix? (ynq)y
au 3507 emap incorrect – fix? (ynq)y
au 3507 summary incorrect – fix? (ynq)y
…………………
au 4653 summary incorrect – fix? (ynq)y
au 4654 emap incorrect – fix? (ynq)y
au 4654 summary incorrect – fix? (ynq)y
au 4655 emap incorrect – fix? (ynq)y
au 4655 summary incorrect – fix? (ynq)y
free block count incorrect 1292071477 expected 39009935 fix? (ynq)y
free extent vector incorrect fix? (ynq)y
OK to clear log? (ynq)y
set state to CLEAN? (ynq)y

After fsck finishes the filesystem is extended and it can be mounted:
root@host:/root# mount /dev/vgora/lvtest /mnt
root@host:/root#

Next step was to make a normal filesystem check:
root@isengard:/# extendfs -F vxfs /dev/vg00/lvora

Similar Posts:

Categories: hp-ux Tags:
  • I want to thank the blogger very much not only for this post but also for his all previous efforts. I found sve.to to be greatly interesting. I will be coming back to sve.to for more information.

  • Really good work about this website was done. Keep trying more – thanks!