Filesystem increase

[Vikas_2]

Hi,
I just now increased the size of my file system with fsadm after running lvextend. The logical volume had one mirror copy also. But it just sitting there for last 15 min...saying
vxfs fsadm: /dev/vgfn/rlvappstaffware is currently 3686400 sectors - size will be increased

In my earlier experience with extending the FS, it happened instantly. Is there something wrong here?? I'm really worried as it's a live FS.

Any suggestions

Thanks in advance

-Vikas

[Steven E. Protter]

When expanding a mirrored volume there is sometimes a delay. It is possible to hang the command if there is no place for the mirror copy, but it should kick out an error.

I'd recommend patience.

SEP

[Vikas_2]

There is enough space on the VG and it has not given any error also yet....It's really becoming very long now.

What may happen if I try to kill it?

-Vikas

[Todd McDaniel_1]

DONT KILL IT!! Let it fail on its own if it will...

Killing can be very bad depending on what operation it is performing.

Is this a mounted filesystem and if so, is there heavy use on it?

Just be patient... let it fail if it will b/c you will get an error message which will help troubleshoot if necessary.

[Helen French]

Did you get any more message on the syslog file? Did you check the output of lvdisplay -v lvol_name? Check if all extents are current. Check the system process status and see if fsadm still running.

If fsadm still runs and if it gives error, I would say fsadm is not configured properly on your system.

[Jeff Schussele]

Hi Vikas,

Do you have a proper lost+found directory in this FS mount point?
By proper I mean one auto-created by newfs or with the mklost+found command. One created with mkdir will not suffice & could be causing trouble here.

Rgds,
Jeff

[Vikas_2]

lvdisplay shows all the extents as current and it reflects new size also. fsadm process is still running and there is a proper lost+fould directory also for this FS.

its more an hour now.

[Jeff Schussele]

Hi (again) Vikas,

Is it possible you may have inadvertently entered Ctrl-S?
Try a Ctrl-Q, you may have locked the terminal session with that Ctrl-S effectively sending an Xoff. The Ctrl-Q will send an Xon.

HTH,
Jeff

[Helen French]

I think either the filesets of fsadm is corrupted or some LVM filesets are corrupted. If you get an error message with fsadm after some time (that fsadm failed), then it's probably the cause. You may have to reinstall those filesets in that case. Also, apply all latest patches too. If you are going to reconfigure those, it would require a reboot.

I would suggest you to go through these Techincal documents too:
TKB # LVMKBRC00010267:
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000066581309

TKB # KBRC00002438:
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000063200461