Showing posts with label File System. Show all posts
Showing posts with label File System. Show all posts

Thursday, 24 November 2011

Extending a VxFS Filesystem (No Online JFS)

Extending a VxFS Filesystem (No Online JFS)

1. Verify that there is enough space in the volume group
vgdisplay
If there is not enough space then the volume group must be extended - see procedure below.

2. First lvextend the logical volume - 2 Options for lvextend:
a. lvextend -L /dev/VG_NAME/LV_NAME
b. lvextend -l /dev/VG_NAME/LV_NAME

3. Unmount the filesystem
4. extendfs -F vxfs /dev//r
Note: extendfs uses the raw logical volume name (ie rlvol1)

A. How to determine if you have Online JFS
swlist -l fileset | grep -i advanced

B. How to determine the filesystem type
grep /etc/fstab
Results should show the filesystem type (vxfs or hfs) in the return string

Add a Lun to a VG in a SG cluster 11.11/23

Once disk presented to host,
# pvcreate /dev/rdsk/cxtxdx
# vgextend /dev/vgname /dev/dsk/cxtxdx
# lvcreate -L /dev/vgname/lvname
# newfs -F vxfs -o largefiles /dev/vgname/rlvname
# cp -p /etc/cmcluster/pkgname/pkg.cntl /etc/cmcluster/pkgname/pkg.cntl.org
# vi /etc/cmcluster/pkgname/pkg.cntl
LV[33]=/dev/vgname/lvname; FS[33]=/oracle/ABN/sapdata20; FSMOUNT_OPT[33]="-o convosync=direct,mincache=direct,delaylog,nodatainlog"
(Add newly create Logical volume to pkg.cnt.file)

# vgexport -p -s -v -m /tmp/vgname.map /dev/vgname
# rcp /tmp/vgname.map nodee2:/tmp/vgname.map
# cp -p /etc/cmcluster/pkgname/pkg.cntl /etc/cmcluster/pkgname/pkg.cntl.node2
# rcp /etc/cmcluster/pkgname/pkg.cntl.node2 nodee2:/tmp/
(mount the mount point manually on the node where the vg is active now)

# mount -o convosync=direct,mincache=direct,delaylog,nodatainlog /dev/vgname/lvolname /oracle/ABN/sapdata20

On Adoptive Node :-
# vgexport /dev/vgname
# mkdir /dev/vgname
# ll /dev/vg*/group
# mknode /dev/vgname/group c 64 0x0X0000
# vgimport -p -s -v -m /tmp/vgname.map /dev/vgname -> (preview) if no error proceed below by removing -p
# vgimport -s -v -m /tmp/vgname.map /dev/vgname
# cp /tmp/pkg.cntl.node2 /etc/cmcluster/pkgname
# cp -p /etc/cmcluster/pkgname/pkg.cntl /etc/cmcluster/pkgname/pkg.cntl.org
# mv /etc/cmcluster/pkgname/pkg.cntl.node2 /etc/cmcluster/pkgname/pkg.cntl

Adding mirroring to the root vg - HP Unix

1. pvcreate -B /dev/rdisk/c2t2d0
Create the PV on the second disk so that LVM can manage it
-B makes it a bootable volume

2. mkboot /dev/rdsk/c2t2d0
Installs the boot files on the second disk

3. mkboot -a "hpux-lq (;0)/stand/vmunix" /dev/rdsk/c2t2d0
Creates an autoboot file on the disk, with information on how to boot

4. vgextend /dev/vg00 /dev/dsk/c2t2d0
extends the volume group to include this second disk.

5. vgdisplay -v vg00
To verify that the second disk is now part of the volume group

6. lvlnboot -v
To verify that the system thinks this disk can boot

7. lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c2t2d0
This extends the logical volume to the mirrored disk, effectively creating the mirrored copy.
This command needs to be run for each logical volume in the volume group

Common NFS errors & solutions

Common NFS errors & solutions:

1."Server Not Responding" Message
2. "Access Denied" Message
3."Permission Denied" Message
4. "Device Busy" Message

Error 1: If You Receive an NFS "Server Not Responding" Message

ping the nfs server from client

1.ping "nfs serer name or ip"

2./usr/bin/rpcinfo -p servername

The rpcinfo command should display the following processes:

* portmap
* nfs
* mountd
* status
* nlockmgr
* llockmgr

If any of these processes is not running, follow the below steps:


a.Make sure the /etc/rc.config.d/nfsconf file on the NFS server contains the following lines:

NFS_SERVER=1
START_MOUNTD=1

b.Make sure that the /etc/inetd.conf file on the NFS server does not contain a line to start rpc.mountd.
If it does, make sure the START_MOUNTD variable in /etc/rc.config.d/nfsconf is set to 0.

c.Issue the following command on the NFS server to start all the necessary NFS processes:

#/sbin/init.d/nfs.server start

Error 2: If You Receive an "Access Denied" Message

a.check the FS is exported or not

#/usr/sbin/showmount -e server_name

(If it is not exported means u have to edit /etc/exports file in NFS server and put the necessary entry and
then run the command
/usr/sbin/exportfs -a)

Error 3 :If You Receive a "Permission Denied" Message

a.Check the mount options in the /etc/fstab file on the NFS client. A directory you are attempting to write to may have
been mounted read-only.

b.Issue the ls -l command to check the HP-UX permissions on the server directory and on the client directory
that is the mount point. You may not be allowed access to the directory.

c.Issue the following command on the NFS server:

/usr/sbin/exportfs

Or, issue the following command on the NFS client:

/usr/sbin/showmount -e server_name

d. Check the export permissions on the exported directory. The directory may have been exported read-only to your client.
The system administrator of the NFS server can use the remount mount
option to mount the directory read/write without unmounting it

Error 4 : If You Receive a "Device Busy" Message

a.If you received the "device busy" message while attempting to mount a directory, try to access the mounted directory.
If you can access it, then it is already mounted.

b.If you received the "device busy" message while attempting to unmount a directory, a user or process is currently using the directory. Wait until the process completes, or follow these steps:

1.Issue the following command to determine who is using the mounted directory:

/usr/sbin/fuser -cu local_mount_point

The fuser(1M) command will return a list of process IDs and user names that are currently using the directory
mounted under local_mount_point. This will help you decide whether to kill the processes or wait for them to complete.

2. To kill all processes using the mounted directory, issue the following command:

/usr/sbin/fuser -ck local_mount_point

3. Try again to unmount the directory.

Extending root file system in HP UX

LVM maintenance mode is not going to help you in this. The problem is that the /stand, swap and /
(the root file system), all need to be contiguous. In order to increase /, you would have to move the lvol
containing /home.
The easiest way to do this is to make an ignite backup tape, boot off it and resize your root logical
volumes at that point.

You can not extend as there is no contigous space available for extending the root volume !

Ignite is the best and safe. Still if you wanna do some LVM tasks, I have documented how to increase
/stand in the following thread. With some slight modifications u can use it for root filesystem as well. I
have tested and it works fine

Here i have adjusted the size of SWAP a bit so that it could be successfully added to the /stand
filesystem ... As you have root filesystem it is more simple as you may have /var or /opt to be moved a
little further and then increase root filesystem.

The Logic is as follows

1. Goto LVM Maintanance Level
2. Find out the next lvol after root lvol
3. Create a similier one somewhere else in the rootvg and create fs on it.
4. Transfer the data to the new filesystem
5. Remove the old filesystem and lvol.
6. You will have contigous space for extending root lvol now !
7. Extend it and resize the filesystem with extendfs
8. Compensate the /etc/fstab as you have changed the device file !
9. Update BOOT,ROOT,SWAP and dump definitions using lvlnboot

REBOOT !!!!!

This is really interesting ... why don't you try this after taking an ignite backup ? If u do a mistake u can
always go back to your ignite !

Notes :- This method will save lots of time ! BUUUUUT never go for this first time w/o a proper
backup !!!!!

EXTENDING BOOT /stand

01. You are not just an "HP kid" who will play with ignite like stuff.

02. You like taking some risk & saving your valuable time

Size of /dev/vg00/lvol1 is A (boot or /stand or /dev/vg00/lvol1)

Size of /dev/vg00/lvol2 is B (swap or /dev/vg00/lvol2)

You wanna increase size of lvol1 from A to A+X (where X is not more than B - "physical memory
installed in your machine")

Basically we have to decrease size of swap to increase boot as they are contigous.

Now Extending /stand is an easy job which can be performed in 10-15 minutes.

Steps

01. Boot your machine in LVM maintenance mode
(hpux -lm at ISL>)

#rm /etc/mnttab
#vgchange -a y /dev/vg00
#lvrmboot -r /dev/vg00
#lvremove /dev/vg00/lvol2
#lvextend -L "A+X" /dev/vg00/lvol1
#extendfs /dev/vg00/rlvol1
#lvcreate -L "B-(X+10)" -C y -r n -n lvol2 /dev/vg00
#lvlnboot -b /dev/vg00/lvol1
#lvlnboot -r /dev/vg00/lvol3
#lvlnboot -s /dev/vg00/lvol2
#lvlnboot -d /dev/vg00/lvol2
#reboot -r

You have your /stand extended now

This is a working solution i have tried & found success

Extending root file system in HP UX

LVM maintenance mode is not going to help you in this. The problem is that the /stand, swap and /
(the root file system), all need to be contiguous. In order to increase /, you would have to move the lvol
containing /home.
The easiest way to do this is to make an ignite backup tape, boot off it and resize your root logical
volumes at that point.

You can not extend as there is no contigous space available for extending the root volume !

Ignite is the best and safe. Still if you wanna do some LVM tasks, I have documented how to increase
/stand in the following thread. With some slight modifications u can use it for root filesystem as well. I
have tested and it works fine

Here i have adjusted the size of SWAP a bit so that it could be successfully added to the /stand
filesystem ... As you have root filesystem it is more simple as you may have /var or /opt to be moved a
little further and then increase root filesystem.

The Logic is as follows

1. Goto LVM Maintanance Level
2. Find out the next lvol after root lvol
3. Create a similier one somewhere else in the rootvg and create fs on it.
4. Transfer the data to the new filesystem
5. Remove the old filesystem and lvol.
6. You will have contigous space for extending root lvol now !
7. Extend it and resize the filesystem with extendfs
8. Compensate the /etc/fstab as you have changed the device file !
9. Update BOOT,ROOT,SWAP and dump definitions using lvlnboot

REBOOT !!!!!

This is really interesting ... why don't you try this after taking an ignite backup ? If u do a mistake u can
always go back to your ignite !

Notes :- This method will save lots of time ! BUUUUUT never go for this first time w/o a proper
backup !!!!!

EXTENDING BOOT /stand

01. You are not just an "HP kid" who will play with ignite like stuff.

02. You like taking some risk & saving your valuable time

Size of /dev/vg00/lvol1 is A (boot or /stand or /dev/vg00/lvol1)

Size of /dev/vg00/lvol2 is B (swap or /dev/vg00/lvol2)

You wanna increase size of lvol1 from A to A+X (where X is not more than B - "physical memory
installed in your machine")

Basically we have to decrease size of swap to increase boot as they are contigous.

Now Extending /stand is an easy job which can be performed in 10-15 minutes.

Steps

01. Boot your machine in LVM maintenance mode
(hpux -lm at ISL>)

#rm /etc/mnttab
#vgchange -a y /dev/vg00
#lvrmboot -r /dev/vg00
#lvremove /dev/vg00/lvol2
#lvextend -L "A+X" /dev/vg00/lvol1
#extendfs /dev/vg00/rlvol1
#lvcreate -L "B-(X+10)" -C y -r n -n lvol2 /dev/vg00
#lvlnboot -b /dev/vg00/lvol1
#lvlnboot -r /dev/vg00/lvol3
#lvlnboot -s /dev/vg00/lvol2
#lvlnboot -d /dev/vg00/lvol2
#reboot -r

You have your /stand extended now

This is a working solution i have tried & found success

How to create EFI & service partition?

1. # vi /tmp/partitionfile
3
EFI 500MB
HPUX 100%
HPSP 400MB
>>then save the file.
2. idisk -wf /tmp/partitionfile /dev/rdsk/c2t0d0 (boot disk path)
3.insf -e
4. pvcreate -fB /dev/rdsk/c2t0d0s2 (boot disk path)
5. mkboot -e -l /dev/dsk/c2t0d0

How t o check disk is bootable or not ?

To display the different bootstrings for a disk:

# lifls

For example:

# lifls /dev/rdsk/c0t6d0

A bootable disk reports something like:

ISL AUTO HPUX PAD LABEL

While a non bootable disk reports:

lifls: Can't list /dev/rdsk/c0t6d0; not a LIF volume

To show the content of the bootentries:

# lifcp : -

For example:

# lifcp /dev/dsk/c0t6d0:AUTO -
hpux

Reduce inode usage?

For examble /opt filesystem's inode usage is high means we have to do below steps

# bdf -i /opt : check the FS usage

Create a test directory on your filesystem;

# mkdir /opt/test

Create a script that will create 10000 null files.

# cd /opt/test
# i=1
# while [ $i -lt 10000 ]
> do
> touch $i
> i=`expr $i + 1`
> done

Else you will be watching the terminal for years to get you the prompt or else CTRL + C will do :-D

once files are created do

#bdf -i /opt

Now comes the step to increase inode count.

# pwd
/opt/test

# rm *
# cd ..
# rmdir test

Now check the inode usage again.

# bdf -i /opt

tar & untar a File ??

TAR
1. tar - cvf test.dat : To tar a file
2.tar -czf test.dat : To tar and zip the file

UNTAR

1. tar -xvf test.tar : To un tar a file.
2. tar -xzf test.tar.gz : To un tar a zipped tar file.
3. tar -xjf test.tar.bz2 : To untar a bzipped file

Enable large file option in hp unix

To change the file system to large file support we need to use below command

#fsadm -F vxfs -o largefiles "/dev/vg00/lvol*"


To mount with large file option

#mount -F vxfs -o largefiles /dev/vg#/lvol# /(mountpoint)

Wednesday, 23 November 2011

Mount ISO image in hp unix : How to ?

On HP-UX 11.11

Start the pfs mount & pfs daemon:

# nohup pfs_mountd &
# nohup pfsd &

create the directory to mount to and run the pfs_mount command:

# mkdir /cdrom
# pfs_mount -o xlat=UNIX /Path/isofile /cdrom

========================

On HP-UX 11.31

Create a new logical volume say ‘isoimage’ of size slightly greater than the size of your iso image in MB.

#lvcreate -L size_of_your_isoimage -n iso /dev/vg01
#dd if=path/to/isoimage of=/dev/vg01/risoimage bs=64
#mount /dev/vg00/iso /cdrom

==========================

How to reduce file system size in unix ??

If online JFS is installed means

#swlist | grep -i "onlinejfs"

#bdf Filesystem
#fuser -cu

Then reduce the Fs size first

#fsadm -F vxfs -b "new size in kb" "Mount Directory"

Ex: fsadm -F vxfs -b 1024 /test

Then reduce the lvol size also

#lvreduce -L "newsize in kb" /dev/vg01/lvolname

Ex: lvreduce -L 1024 /dev/vg01/lvol2


If online JFS not installed means

1. Backup all user data

2. Umount the filesystem
#umount /home

3. Reduce the size
#lvreduce -L "size" /dev/vg01/lvolname

4. Re-create the filesystem

#newfs -F vxfs /dev/vg01/rlvolname

5) Mount the Logical Volume:
mount /dev/vg01/lvolname /mountdir

6) Restore the user data

Recover rootvg (vg00) using ignite tape backup

Take the Root vg (vg00) backup @ tape drive use the below command

# make_tape_recovery -v -x inc_entire=vg00 -a

#make_tape_recovery -I -v -x inc_entire=vg00 -a /dev/rmt/0mn

The tape will be completely erased and recreated when you run the command.

Recover VG00 - Boot with backup tape:

Reboot the system, ON IPL do sea ipl. this will list tape device.

IPL>sea ipl
IPL>bo from p1(assuming p1 is tape device)

This wil start interactive HP-UX install.

Upgrade VXFS Online

update version 3 veritas JFS file system to version 4

vxupgrade -n 4 /mount_point

vxfsconvert -- offline version or to convert an HFS

fsadm: cannot open /directory/lost+found - how to fix this error?

If u got the below error..

# fsadm -F vxfs -b 20448M /directory
vxfs fsadm: cannot open /directory/lost+found/.fsadm - errno 2

Follow the below steps to fix this error..

#ls /directory --- no lost+found there.


# cd /directory

# mklost+found
creating slots...
removing dummy files...
done


now run fsadm it will get complete..

Dump device is too small ? : AIX

- Thanks to Michelle.

1) # /usr/lib/ras/dumpcheck –p
Also you can find the output from # errpt -a
The Output as below:
The largest dump device is too small.
Largest dump device
dumplv01
Largest dump device size in kb
3538944
Current estimated dump size in kb
3561676

Synchronizing

# lsvg rootvg

VOLUME GROUP: rootvg VG IDENTIFIER: 00cdd76d00004c00000001079dbde229
VG STATE: active PP SIZE: 128 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 2184 (279552 megabytes)
MAX LVs: 256 FREE PPs: 1995 (255360 megabytes)
LVs: 12 USED PPs: 189 (24192 megabytes)
OPEN LVs: 11 QUORUM: 1
TOTAL PVs: 4 VG DESCRIPTORS: 4
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 4 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable

FREE PPs shows you have 25GB free on the rootvg and your PP Size is 128mb (IE you can allocate fs extentions in 128mb chunks)

Now show your dump devices :
# sysdumpdev -l

primary /dev/lg_dumplv
secondary /dev/lg_dumplv2
copy directory /var/adm/ras
forced copy flag TRUE
always allow dump TRUE
dump compression OFF

# lslv lg_dumplv
LOGICAL VOLUME: lg_dumplv VOLUME GROUP: rootvg
LV IDENTIFIER: 00cdd76d00004c00000001079dbde229.10 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: sysdump WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 128 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 9 PPs: 8
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: N/A LABEL: None

8PPs*128mb*1024 = 1048576 which matches the current size

Calculate the new dump size from the high water mark

1049600/1024/128 = 8.0078125 !!!! Hmmm ok so allocate one more PP just to keep it happy (bad example - I have had to add 12PPs on systems before)

Extent the dumpdev :

# extendlv lg_dumplv 1

# lslv lg_dumplv

LOGICAL VOLUME: lg_dumplv VOLUME GROUP: rootvg
LV IDENTIFIER: 00cdd76d00004c00000001079dbde229.10 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: sysdump WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 128 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 9 PPs: 9
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 32
MOUNT POINT: N/A LABEL:

New size!

Now clear the error
# errclear 0

How to enable Quota in HP UX ?

Note: Thanks to Shameer For sharing this Tips.


Enable the HPUX default quota by following steps:


For each file system for which quotas are to be enabled, perform the following tasks:
1. Mount the file system.
2. Add quota to the existing options list in /etc/fstab. For
example, change the string default for the root (/) entry to
default,quota. Once this is done, quotas will automatically
be enabled for all relevant file systems on system reboot.
3. Create the quotas file in the mount directory of the file
system. For example, for the /mnt file system, run the
command
cpset /dev/null /mnt/quotas 600 root bin
4. Establish one or more prototype user quotas using the
edquota command (see edquota(1M)).
If you want a number of users on your system to have the
same limits, use edquota to set those quotas for a prototype
user; then use the edquota -p command to replicate those
limits for that group of users.
5. Turn on the quotas on the file system using quotaon. For
example, run the command
/usr/sbin/quotaon /mnt
6. Run quotacheck (see quotacheck(1M)) on the file system to
record the current usage statistics.

Adding a new user

To add a new user to the quota system:
1. Use edquota to copy the quotas of an existing user.
2. Run quotacheck.

Adding a new file system to an established system

Repeat steps 1 through 5 above under "Initial Setup" for the new file
system.

======================================================================================


We can enable the HPUX default quota by following steps:

1) mount the corresponding file system using the quota option

2) Activate the quota.
2) specify users with the quota limit for the file system

I'm hereby giving an example of enabling quota for my user id user1.

STEP: 1. Mount the file system in quota mode.

# mount |grep quota
/quotatest on /dev/vg00/lv_test quota,delaylog on Wed Oct 19 16:13:39 2011
#

STEP :2 Edit the quota for the user ( inthis example for user1)

serverA {root}# edquota user1
"/var/tmp/EdP.a18825" 1 line, 71 characters
fs /quotatest blocks (soft = 1024, hard = 2048) inodes (soft = 0, hard = 0)
~
"/var/tmp/EdP.a18825" 1 line, 76 characters

STEP 3 : Check the quota status.

# quota -v
Disk quotas for user1 (uid 44312):
Filesystem usage quota limit timeleft files quota limit timeleft
/quotatest 7 1024 2048 3 0 0


STEP 4 : Create test files to increase the usage for the user "user1" in the specific file system. Warning message will be displayed if the soft limit is crossed.

#cd /quotatest/user1

# ls -lrt
total 14
-rw-r----- 1 user1 osg 6000 Oct 19 16:22 testfile
-rw-r----- 1 user1 osg 500 Oct 19 16:23 testfile3

# prealloc testfile4 50000000
msgcnt 6 vxfs: mesg 044: vx_bsdquotaupdate - warning: /quotatest file system user 44312 disk quota exceeded
prealloc: Disk quota exceeded

# quota -v
Disk quotas for user1 (uid 44312):
Filesystem usage quota limit timeleft files quota limit timeleft
/quotatest 937 1024 2048 6 0 0


STEP 5 : Create test files to increase the usage for the user "user1" in the specific file system to cross the threshold. Error message will be displayed if the
hard limit is crossed that the quota is exceeded.

# prealloc testfile7 450000
msgcnt 10 vxfs: mesg 044: vx_bsdquotaupdate - warning: /quotatest file system user 44312 disk quota exceeded

# ls -lrt
total 2752
-rw-r----- 1 user1 osg 6000 Oct 19 16:22 testfile
-rw-r----- 1 user1 osg 500 Oct 19 16:23 testfile3
-rw-r----- 1 user1 osg 50000 Oct 19 16:34 testfile4
-rw-r----- 1 user1 osg 450000 Oct 19 16:36 testfile5
-rw-r----- 1 user1 osg 450000 Oct 19 16:37 testfile6
-rw-r----- 1 user1 osg 450000 Oct 19 16:37 testfile7

# quota -v
Disk quotas for user1 (uid 44312):
Filesystem usage quota limit timeleft files quota limit timeleft
/quotatest 1377 1024 2048 7.0 days 7 0 0

fsadm: You don't have a license to run this program : how to fix??

If u got the below error

fsadm -b 1024M /home/user1
fsadm: /etc/default/fs is used for determining the file system type
fsadm: You don't have a license to run this program

1. # /usr/sbin/vxlicrep -e

Check the valid Liscense

2. # vxlicense -p vxlicrep

Check the valid license from running server and install it on this server

License location : # /etc/vx/elm

# ll /etc/vx/elm

total 32
-rw-r--r-- 1 root sys 171 Nov 4 14:43 50.lic
-r--r--r-- 1 bin bin 291 Nov 14 2000 README

Copy the 50.lic file to the required server and install it

3. # vxlicinst -k 010449565889805115946465 (install the license)

4. # sbin/fs/vxfs/vxenablef -a (Enable that license)

Now u can try to extend the FS

# fsadm -b 1024M /home/user1

Buffer cache ON/OFF for file system in HP UX:How to ??

Why buffer cache ?
Buffer cache stores recently read data in memory to help reduce the amount of I/O to physical disks. This is advantageous when the same data is accessed many times as the data can be served directly from memory.

How to Turn ON /OFF ?

File systems use Buffer cache by default. To stop a file system using Buffer cache the following mount options are used:
mincache=direct,convosync=direct
These options can be changed on the fly without umounting the filesystem by using the remount option to the mount command.

mount -F vxfs -o remount,

To make the file system use buffer cache again, remount the file system without the mincache and convosync options.