Operating System - HP-UX
1832778 Members
3050 Online
110045 Solutions
New Discussion

erros message after adjusting lvol5

 
Scott McDade
Frequent Advisor

erros message after adjusting lvol5

I was running out of space in lvol5 (/opt) so I adjusted it via SAM. Shortly after I adjusted it I began getting System messages from one of my applications stating that the "Filesystem '/opt/(mounted on /dev/vg00/lvol5)' is 226 % used. Which is totally inaccurate. So I started working with the one of the developers of the application who told me that they check the size and used cluster by system call. And it appears as if HP-UX defects or mis-operation that the informatin does not change/update of size change. As the result, the calculation becomes over 100%.

So the application developer thinks it is a HP-UX issue. Has anyone else seen this type of probelm with the system call and if so how was it resolved?


Keep it Simple!~
3 REPLIES 3
Insu Kim
Honored Contributor

Re: erros message after adjusting lvol5

You should first umount the adjusted logical volume and mount it again to reflect the updated size information to the system if you have used Online-JFS, sometimes.

Hope this helps.
Never say "no" first.
Chris Maehara
Occasional Advisor

Re: erros message after adjusting lvol5

MeasureWare may be the culprit. If you are running it and monitoring the size and usage of the file systems, then you need to stop and restart the MeasureWare daemons.
Shahul
Esteemed Contributor

Re: erros message after adjusting lvol5

Hi


Whenever U want to do any changes in in any filesystem, It is better to unmount. In ur case it may not allow to unmount, because filesystem may be in Use. In that case always better to boot in lvm maintanence (type hpux -lm in ISL prompt) mode and do the modification.

Best method I will list down

Boot thru lvm maintanence mode

#vgchange -a y vg00
#lvextend "new size" /dev/vg00/lvol5
#extendfs /dev/vg00/rlvol5
#mount -a
#bdf

Now ur file system size should be OK. Then reboot in normal mode. If U do like this U could have avoided the above error message.

Best of luck

Shahul