bdf vs lvdisplay

[Lise Love-Thompson]

I added 4 new disks to the disk array. I created a new LUN. It uses an existing volume group. I extended the size of a logical volume (from 15G to 30G). lvdisplay shows 30K. bdf shows 15k. Why?

Thanks.

[James R. Ferguson]

Hi:

Have you done an 'extendfs' or 'fsadm -b' as appropriate? If you have only completed the ;lvextend', then 'bdf' will not show the resize filesystem because it hasn't yet been resized.

Regards!

...JRF...

[melvyn burnard · Accepted solution]

lvextend is only half the job ;-}
You have increased the "disk" capacity, but not the file system size.
you need to unmount the file system and do an extendfs on it, then mount it again.
Or if you have OnlineJFS you can extend the filesystem on line
bdf should now show the correct file system size

[Lise Love-Thompson]

I used SAM to increase the size. I think something was stuck because of paging in it. Isn't it right?

[James R. Ferguson]

Hi (again) Lise:

I don't use SAM for disk and filesystem configuration. I've seen SAM hangup trying to unmount a filesystem.

In any event, you should be able to 'extendfs' or use 'fsadm -b' (if you have OnlineJFS) to complete the process.

If you do not have OnlineJFS, unmount the filesystem and do:

# extendfs /dev/vgXX/rlovlX #...note raw device
# mount /dev/vgXX/lvolX /

If you are using OnlineJFS there is no need to unmount:

# fsadm -b /

...where is the number of 1K blocks (1K=1024). Thus if you did 'lvextend -L 100' your would be 100*1024 or 102400.

Regards!

...JRF...

[Sridhar Bhaskarla]

If SAM completed the job successfully and if you are still seeing the problem, then I would suggest to unmount and mount it again.

If it still didn't fix the problem, do an extendfs manually on the character device of the logical volume.

-Sri

[Lise Love-Thompson]

Ok, thanks. I will try it tonight. Hope it will work.

[A. Clay Stephenson]

Hi Lise:

Make sure that filesystem you are trying to extend has a lost+found directory. If the file lost+found/.fsadm cannot be written, the will hang SAM everytime.

[Lise Love-Thompson]

I couldn't dismount a file system on level 3 and lower run levels because the device kept "busy". I found out that it's stuck with the swap file system so I removed the swap file system. I finally dismounted the file system and did extendfs it successfully. After that, I recreated the swap filesystem in it. I believe that's why it couldn't change yesterday because of the swap file system. Thanks very much for your help!

[Animesh Chakraborty]

Hi,
You said "I couldn't dismount a file system on level 3 and lower run levels because the device kept "busy". I found out that it's stuck with the swap file system so I removed the swap file system. "....
How can it stuck with swap file system ?Did you mention wrong LV name ? i.e. swap's lv ?

Thanks
Animesh

[Sanjay_6]

Hi Animesh,

I think what lise wants to convey is that the logical volume she wants to extend has secondary/filesystem swap in that lv. Hence she was not able to extend the filesystem. She removed that secondary swap today and so was able to extend the filesystem.

hope this is the situation.

Thanks

[Lise Love-Thompson]

That's correct. Thanks.