/var and largefiles

[Darren Etheridge_2]

I am considering modifying /var to use largefiles (for Data Protector Database). Is there any caveats to this or should I not even consider doing so to the UX main filesystem?

THanks!

[Pete Randall · Accepted solution]

I use largefiles on all my root file systems except /stand and / with no problems. If there's a caveat, I haven't blundered into it yet.


Pete

[SoorajCleris]

Hi,

I think var must be already with largefiles. You can check with #fstyp command.

But if it is not , then how you are going to do that ?


Regards,
Sooraj

[James R. Ferguson]

Hi Darren:

There is no problem with doing this.

Regards!

...JRF...

[Darren Etheridge_2]

I have Online JFS, so what is the best way to change it to largefiles?

[Patrick Wallek]

With the fsadm command.

# fsadm -o largefiles /var

Will change /var to have large files enabled.

Also check your /etc/fstab file and see if the line for /var mentions largefiles or nolargefiles. If it does not, that is OK.

[Patrick Wallek]

I should have mentioned that you can also use fsadm to check the filesystem.

# fsadm /var

Will should show 'largefiles' after you run the 'fsadm -o' command above.

[Darren Etheridge_2]

This is the output I get from running the command:

[TAL:/]fsadm /var
fsadm: /etc/default/fs is used for determining the file system type
largefiles


but when running cat /etc/fstab i get:

/dev/vg00/lvol8 /var vxfs delaylog 0 2



my other filesystems with largefiles enabled shows largefiles, this one does not.

[James R. Ferguson]

Hi (again) Darren:

Largefiles is enabled for your '/var'. The presence of 'largefiles' or 'nolargefiles' in '/etc/fstab' is only to enforce the underlying filesystem value. The filesystem attribute must match that of the attribute in '/etc/fstab' in order for the mount operation to succeed.

Regards!

...JRF...

[Robert-Jan Goossens]

Hi,

Add the largefiles option to the /etc/fstab

largefiles,delaylog

Regards,
Robert-Jan