cluster fs bad.

[fizan]

while trying to add additional disks to vg which runs on a cluster. the error throws.

halted pkg cmhaltpkg sappkg
done.

lvextend -- done.

extendfs -F vxfs /dev/sapvg/rsaplv
vxfs extendfs: V-3-20140: FS is dirty, run fsck first.
[rx26-184]/
# fsck -y /dev/sapvg/rsaplv
fsck: /etc/default/fs is used for determining the file system type
log replay in progress
intent log does not contain valid log entries
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
flush fileset headers? (ynq)y
set state to CLEAN? (ynq)y
[rx26-184]/
# extendfs -F vxfs /dev/sapvg/rsaplv
vxfs extendfs: V-3-20140: FS is dirty, run fsck first.
[rx26-184]/
# fsck /dev/sapvg/rsaplv
fsck: /etc/default/fs is used for determining the file system type
log replay in progress
replay complete - marking super-block as CLEAN
[rx26-184]/
# extendfs -F vxfs /dev/sapvg/rsaplv
vxfs extendfs: V-3-20140: FS is dirty, run fsck first.
[rx26-184]/
#

[sen_ux · Accepted solution]

Try a fsck with full option.

#fsck -o full,nolog /dev/sapvg/rsaplv

thanks

[singh sanjeev]

which version of us u r running...is online jfs is installed.

do fsadm after lvextend to grow the FS.

Fsadm -b M

[fizan]

swlist |grep JFS
B3929EA B.11.31 HP OnLineJFS (Server)

[singh sanjeev]

if you are creating a new lv then use ,

newfs -F vxfs -o largefiles -b 8192 /dev/sapvg/rsaplv

for growing the FS after extention use ..fsadm

[fizan]

from the swlist it shows as online jfs

fine extendfs works out but.. it shows
error as vxfs extendfs: V-3-20140: FS is dirty, run fsck first

Excatly to say after showing the fsck error.
i checked the lvsize it has been increased, as
lvdisplay -v /dev/sapvg/saplv |more
--- Logical volumes ---
LV Name /dev/sapvg/saplv
VG Name /dev/sapvg
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 21488
Current LE 5372
Allocated PE 5372
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c9t1d1 2303 2303
/dev/dsk/c17t1d0 1023 1023
/dev/dsk/c17t0d7 1023 1023
/dev/dsk/c17t0d6 1023 1023
finally added 3 pv's.
am afraid after cmrunpkg fs issue ill come.

[fizan]

finished by adding disks & lvextend.

but after fsck it showed error.



thanks

[SoorajCleris]

Is there any other error in syslog?

As this is a cluster system , what it says if you are running the same command from other system?

Regards,
Sooraj

[AnthonySN]

halt the pkg.
activate the vg in exclusive mode.
do the changes.
dont forget to vgeport and vgimport the map on bot the nodes before starting the pkg again.

[S.N.S]

SASJ,I doubt that is the issue.

As said, error do you get from syslog?

Also, please confirm if the full fsck check was successful, before we go any further:

fsck -F vxfs -o full -y /dev/dsk/rsaplv

This prev. thread may help you:
http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1272206399330+28353475&threadId=840617

Let Us know your progress soon.

HTH
SNS