topic online JFS in Operating System - HP-UX

online JFS

Jeffrey F. Goldsmith — Tue, 29 May 2007 19:04:06 GMT

This afternoon I was asked to increase one of my logical volumes from 4GB to 6GB. I started SAM and increased the LV size and just before it was done I got an error. (Sorry that I didn't write it down).

I see that the size was increased but when I try to extendfs the file I get the following error:

root: /apps ==> extendfs /dev/vg01/devifas
vxfs extendfs: FS is dirty, run fsck first.
root: /apps ==> fsck /dev/vg01/devifas
vxfs fsck: file system had I/O error(s) on meta-data.
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 ...

I am going to do a search on full fsck to see how to perform that task.

Thanks for any help.

Re: online JFS

A. Clay Stephenson — Tue, 29 May 2007 19:30:34 GMT

It's a bi confusing when you mention extendfs and OnlineJFS. You only run extendfs on an unmounted filesystem. The correct command for a mounted filesystem is fsadm -F vxfs -b size

In any event, you will need to run
fsck -F vxfs -o full,nolog /dev/vg01/rdevifas

Re: online JFS

A. Clay Stephenson — Tue, 29 May 2007 19:30:40 GMT

It's a bit confusing when you mention extendfs and OnlineJFS. You only run extendfs on an unmounted filesystem. The correct command for a mounted filesystem is fsadm -F vxfs -b size

In any event, you will need to run
fsck -F vxfs -o full,nolog /dev/vg01/rdevifas

Re: online JFS

Jeffrey F. Goldsmith — Wed, 30 May 2007 11:21:43 GMT

I tried to use the Online JFS to increase the space and received an error. The reason I used Online JFS was so that I could increase the space while the LV was mounted. After getting the error I umounted the LV and tried to extend the LV. The LV showed that it was increased but was giving me trouble because it wasn't totally unmounted.

After doing some reasearch I found that I still had one deamon running so after I stopped that deamon the LV was unmounted. When I tried to extend the LV I received another error.

root: /apps ==> extendfs /dev/vg01/devifas
vxfs extendfs: FS is dirty, run fsck first.

So, I tried to run fsck and received another error.

root: /apps ==> fsck /dev/vg01/devifas
vxfs fsck: file system had I/O error(s) on meta-data.
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 ...

I finally had to run the fsck -y to get the LV cleaned up.

root: /apps ==> fsck -y /dev/vg01/devifas
vxfs fsck: file system had I/O error(s) on meta-data.
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
OK to clear log? (ynq)y
set state to CLEAN? (ynq)y

After that I was able to extend the LV and get it mounted.

Any idea as to why I couldn't use Online JFS to increase the LV size and why the file got messed up?

Re: online JFS

A. Clay Stephenson — Wed, 30 May 2007 11:41:28 GMT

A common reason for fsadm -F vxfs -b larger_size to fail is that there is not sufficient free space in the filesystem. You need a little free space before issueing the command.

Re: online JFS

Geoff Wild — Wed, 30 May 2007 12:52:15 GMT

Well - what probably happend was you tried online JFS first - so you lvextended the lvol.

As Clay says - if the fs was 100% full - then it would fail on the fsadm

The other thing is - if you typed the command wrong - it would fail...

IE - if you did:

lvextend -L 6144 /dev/vg01/devifas

then

fsadm -b 6144 /yourmount_point

yes - it would fail - as you forgot the M for MB:

fsadm -b 6144M /yourmount_point

Rgds...Geoff