Operating System - HP-UX
1756007 Members
3690 Online
108839 Solutions
New Discussion юеВ

Conflicting information between Logical Volumes and File Systems

 
Carlo Iaboni
Occasional Contributor

Conflicting information between Logical Volumes and File Systems

I am installing patches, and the installs fail due to lack of space on the /opt file system (/dev/vg00/lvol6).
In SAM, the FILE SYSTEMS DISPLAY shows:

Unused MBytes 370 Total Mbytes: 772

the LOGICAL VOLUMES DISPLAY shows:

Logical Volume Size (Mbytes): 512

and lvdisplay shows:

# lvdisplay /dev/vg00/lvol6
--- Logical volumes ---
LV Name /dev/vg00/lvol6
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 512
Current LE 128
Allocated PE 128
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

I raised the LV size from 512 to 772 using the lvextend command.
Can anyone explain why the size of the logical volume did not increase?

I have tried many times to do the increase in SAM but the Lvol is busy and cannot be unmounted.
5 REPLIES 5
Adisuria Wangsadinata_1
Honored Contributor

Re: Conflicting information between Logical Volumes and File Systems

Hi,

If you extend the file system using basic LVM (not OnlineJFS), you need to apply 'extendfs' after 'lvextend'.

To perform this 'extendfs' you need to umount the file system which is can be done on the single user mode.

So here is the steps :

1. goto single user mode
2. umount the file system
3. extend the file system

For details, check the manpage of the command :

# man extendfs
# man lvextend

Hope this information can help you.

Cheers,
AW
now working, next not working ... that's unix
Bill Hassell
Honored Contributor

Re: Conflicting information between Logical Volumes and File Systems

lvextend just makes the lvol bigger. Logical volumes can contain many different items: swap space, raw database, or a filesystem. The filesystem knows nothing about this change so it will not expand. That's why you need to inform the filesystem of this change with extendfs. But because the filesystem needs to be reorganized, the filesystem must be unmounted.

The only way to extend a filesystem without unmounting is to purchase and install the Online JFS product.


Bill Hassell, sysadmin
Sivakumar TS
Honored Contributor

Re: Conflicting information between Logical Volumes and File Systems


Hi,

Though lvol size has been increased, the USABLE/ACCESSABLE space is only the Filesystem area.

Hence, after increasing the lvol size we have to manually extend the filesystem too.

This can be done using #extendfs / #fsadm ( incase of Online JFS).

If you do not have Onlne JFS , then the filesystem can not be modified/extended on the FLY.

With Regards,

SIva.
Nothing is Impossible !
Tvs
Regular Advisor

Re: Conflicting information between Logical Volumes and File Systems

hi.


your sucessfully increased the logical volume. but you need to incease the file system also. you can do this online if onlinejfs is installed ( check swlist -l fileset | grep -i online)


if online jfs installed ..

#fsadm -b 772M /opt

if not installed
# umount /opt ( make sure no body using /opt fs... or u can kill all the process #fuser -k /opt)
#extendfs -F (fs type ) /dev/vg00/rlvol6

regards

Tvs
Steven E. Protter
Exalted Contributor

Re: Conflicting information between Logical Volumes and File Systems

Without OnlineJFS, you need to set a maintenance window and use extendfs to make the filesystem bigger.

When sam is giving conflicting information, take a look at command log and try those command at the command line.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com