mount problem while enableing largefiles support in HP-UX 11.00

[Aviad Twina]

Hi gurus,
I'm trying to enable largefiles support in an existing file system without any success.
I've tried the fsadm option
/usr/sbin/fsadm -F -o options vxfs /dev/vg00/lvol4 /tmp (but it didn't help.

init s
I managed to umount the /tmp and with the "sam"
utility I enabled the largefiles support.
remounted the /tmp and reboot.
Once the machine was up I was able to see the largefiles option in the fstab, however the /tmp mount has gone, and the new /tmp appears under / .
What did I do wrong?
Please help,
Thanks,
Aviad

[Steven E. Protter]

Here is a valid /etc/fstab entry to mount a fs that has been created enabled for large filesystems.


# /dev/vg01/oracle6 /oracle6 vxfs rw,suid,largefiles,delaylog,datainlog 0 2
I have it commented.

The fs must have either been created with newfs -F vxfs -o largefile /dev/vg00/....

or with the fsadm command you ran.

check /etc/fstab

Note that for 11.11 the largefiles directive is not permitted in /etc/fstab

SEP

[Sridhar Bhaskarla]

Hi,

If you have Online-JFS installed, you would use the command

fsadm -o largefiles /tmp

If you don't have online-JFS, then it is advisable to boot the system into single user mode as there is little chance that you can unmount /tmp in multi-user mode. Once /tmp is unmounted, in single user mode, do

#mount /usr
#mount /var
#/usr/sbin/fsadm -F vxfs -o largefiles /dev/vg00/lvol4
#mount /tmp
#init 3

In your case, it is most probably that /tmp (directly under /) is busy so the logical volume is not being able to get mounted.

Try mounting it manually

#mount /dev/vg00/lvol4 /tmp

If it says it's "busy", then you will have to reboot the system to make things clean.

-Sri

[Uday_S_Ankolekar]

fsadm -F vxfs -o largefile /mountpoint and change it in fstab by adding largefile
To verify use mkfs -F vxfs -m /dev/vgnn/lvolnn

-USA..

[Paul Sperry]

here is an entry from my 11.11 system

/dev/vg00/ifasvol /ifas vxfs delaylog,nodatainlog,largefiles,rw,suid 0 2


try

/usr/sbin/fsadm -F vxfs -o largefiles /dev/vg00/lvol4 /tmp

[Aviad Twina]

The referance for /tmp in /etc/fstab looks like this:
dev/vg00/lvol4 /tmp vxfs rw,suid,largefiles,delaylog,datainlog 0 2
But still after i do mount | grep /tmp
I don't see the /tmp.
It seems like the fstab cannot mount /tmp after the change i've made.
Thanks,
Aviad

[Sridhar Bhaskarla]

Hi Aviad,

Please post the message you get when you do

#mount /tmp

-Sri

[Jeff Schussele]

Hi Aviad,

I notice no one has quetioned just *why* you need largefiles enabled in /tmp.
IMHO, this is not a good place to be creating +2Gb files.
We only size out /tmp @ 256Mb.
You should really rethink just why someone/something *needs* to be creating largefiles in /tmp.

If an app needs to store largefiles in a "temp" dir then have the user set the TMPDIR variable pointing to an appropriate location outside of vg00.

My 2 cents,
Jeff

[Tim Sanko]

To add to Jeff's comments, I have a large /tmp of 2GB on our q6 Way V-Class production box. It isn't set up to allow large files. IMHO /tmp is a bad place for > 2 GB files.

I have that large a /tmp because of an application that keeps active traces in tmp. otherwise I would use a
256 MB or there abouts.

Tim

[Tim Sanko]

16 Way V-Class

[Aviad Twina]

fellowes,
This is a QA machine, and i'm testing the largefiles support before i'll enable this options on production server.

mount -a
mount: /dev/vg00/lvol6 is already mounted on /var
mount: /dev/vg00/lvol5 is already mounted on /usr
vxfs mount: /dev/vg00/lvol4 is already mounted, /tmp is busy,
or allowable number of mount points exceeded
mount: /dev/vg00/lvol1 is already mounted on /stand

[Sridhar Bhaskarla]

Hi,

This means /tmp (directly under /) directory is busy. Make sure you are not in /tmp directory.

Verify if largefiles have been enabled on lvol4 before you reboot the box.

#mkfs -m /dev/vg00/lvol4

Observe the output for largefiles. If it indicates nolargefiles, then use
#fsadm -F vxfs -o largefiles /dev/vg00/lvol4

Use fuser to find out what processes are accessing /tmp directory.

fuser /tmp

Look at the processes. If you can kill them, do so, else you may have to reboot the box. Once fuser returns nothing, try doing mount -a again.

-Sri

[Aviad Twina]

Sridhar,
The output of the mkfs -m command observes nolargefiles.
However, when i use fsadm -F vxfs -o largefiles /dev/vg00/lvol4 I get "fsadm -F vxfs -o largefiles /dev/vg00/lvol4 "
Thanks,
Aviad

[Sridhar Bhaskarla]

It should have been "rlvol4". Try
fsadm -F vxfs -o largefiles /dev/vg00/rlvol4.
Haven't had evening coffee yet.

-Sri

[Aviad Twina]

Sridhar,
It works !
Thanks a lot.
Aviad