unable to extend LV

[Randy_9]

I get the following error message when trying to extend an LV:

The command used to resize a VxFS f/s has failed.
vxfs fsadm: /var/adm/sw is not the root inode of a vxfs file system.

The LV as listed in /etc/fstab:
/dev/vg00/var_adm_sw /var/adm/sw vxfs delaylog 0 2

Show's up as a LV in SAM (from
which I tried to extend it)?

Thanks,

Randy

[Sandip Ghosh]

I may be wrong, but as per the error message it seems your /var/adm/sw filesystem is not mounted at present. Can you please post the command you had given?

Sandip

[steven Burgess_2]

Hi

What does the server think is mounted

grep /var/adm/sw /etc/mnttab

Regards

Steve

[Bill McNAMARA_1]

mount -p
shows which fs's are currently mounted,

mount -a
will mount all in /etc/fstab,

what is your commandline:

lvextend -L new_MB_size /dev/vg00/var/adm/sw

or are you doing and

extendfs -F vxfs /var/adm/sw

?

Later,
Bill

[S.K. Chan]

Are you using fsadm to extend it (online perhaps) ? If that's the case this error usually means you've issue a wrong syntax (for example not using raw device path), or the FS that you're extending is not mounted.

[Randy_9]

All,

I was using SAM to extend it. I had stopped "swagentd" prior to and umounted it manually first. When mounted the device name is the same in both /etc/fstab and etc/mnttab. Strange thing is now:
SAM is showing it as being extended (to 700MB) while
a "bdf -l" shows it at 400MB
when mounted.
Now what?

Points assigned.

Thanks,

Randy

[S.K. Chan · Accepted solution]

Forget SAM for a moment. I've had "ugly" experience with it which I would not want to talk about it here. Check ..
# vgdisplay -v vg00|more
=> Does the "var_adm_sw" LV shows the new size that you have extended to ?
# bdf -l
=> Again run this, does the FS size match up with that of LV size ?
If not manually umount it again and run extendfs on it.
# umount /var/adm/sw
# extendfs -F vxfs /dev/vg00/rvar_adm_sw
# mount -a
# bdf -l
Does it shows up fine now ?

[Helen French]

What about the lvdisplay output? Is it showing the new size? If you 've not patched the system properly, then you may experience these type of errors.

# lvdisplay -v /dev/vg00/var_adm_sw

[MANOJ SRIVASTAVA]

Randy

can you run it from the command line like

lvextend -L (size)/dev/vg00/rvar_adm_sw


and then fsadm /var/adm/sw




Manoj Srivastava

[Randy_9]

S.K. Chan,

The vgdisplay showed it at 700MB, but "bdf -l" did not. I umounted it and was able to extend it via the command line. SAM... ughhh!

S.K. and Manoj,

Do I still need to run "fsadm", I have already remounted it and "bdf -l" is now showing the correct size.

Thanks all, points assigned!

Randy

[S.K. Chan]

No, all you do is lvextended your LV with the filesystem umounted, there is no need for "fsadm" command at all. The "fsadm" typically deal with MOUNTED filesystem. For example ..
- increasing mounted FS on-the-fly
- fragmentation report
- defragmentation

[Randy_9]

Thanks everyone for the great help!

Randy