largefiles

[Tarek]

Hi all,
i have a problem concerning largefiles. During installation i think i have enabled them, but some users says i haven't. To check that i'm issueing this command:
fsadm -F vxfs /dev/vg00/lvol4 (that corresponds to my /local_user).
But i'm having this error:
vxfs fsadm: /dev/vg00/lvol4 is not the root inode of a vxfs file system.
What is the problem? then is it correct what i will do:
umount -a
fsadm -F vxfs -o largefiles /dev/vg00/lvol4
mount
thanks in advance

[Shahul]

Hi

This error will come if ur file system is hfs. I mean ur file system is hfs and U are issuing command for vxfs. Run command like this and see

#fsadm -F hfs /dev/vg00/lvol4

No need of unmounting the filesystem.

Best of luck


Shahul

[Carsten Krege · Accepted solution]

When working on an unmounted filesystem, use the raw device (rlvol4)!

I setup a new filesystem and added the largefile bit, here on a mounted filesystem.

# newfs -F vxfs /dev/vgburn/rlvol2
version 3 layout
4096 sectors, 4096 blocks of size 1024, log size 128 blocks
unlimited inodes, largefiles not supported
4096 data blocks, 3896 free data blocks
1 allocation units of 32768 blocks, 32768 data blocks
last allocation unit has 4096 data blocks
# mkdir /sepp
# mount /dev/vgburn/lvol2 /sepp
# fsadm -F vxfs /sepp
nolargefiles
# fsadm -F vxfs -o largefiles /sepp
vxfs fsadm: set feature (LARGEFILES) failed, errno 251
# fsadm -F vxfs /sepp
largefiles


Problem: When using fsadm with the -o largefiles option, fsadm may report a failure even though the command was successful. For example:

#fsadm -F vxfs -o largefiles /filesystem
vxfs fsadm: set feature (LARGEFILES) failed, errno 251
A check of the file system will show if the command was successful in setting the largefiles flag.

Workaround: To check if the largefiles flag is set, use

fsadm -F vxfs /filesystem


Carsten

[Tarek]

Hi Shahul,
my filesystem is vxfs and not hfs. Then i have to unmount because i need to enable largefiles and this isn't possibile if the filesystem is mounted

[Frank Li]

command :

fsadm /dirrectory
will be okay.

[Frank Li]

Or you should use the charactor device file .

fsadm -F vxfs /dev/vg00/rlvol4

fsadm -F vxfs -o largefiles /dev/vg00/rvol4

[Atil Volkan Yildirim]

use the character device files when issuing fsadm commands(sure u have to umount vxfs)...also when first creating,use:
newfs -F vxfs -o largefiles /dev/vgxx/rlvyy;
********************************************
or umount the file system and try to mount with:
mount -F vxfs -o largefiles /dev/vgXX/lvYY /mp

*********************************************
to check:
fstyp -v /dev/vgXX/rlvYY
the f_flag=16 means largefiles option is enabled,zero means nolargefiles...

**********************************************

or try to issue the following command with a user account and obsorve the output:
# prealloc bigfile 2200000000

**********************************************

regards...

[Fabien DISSON]

Just a little precision:
you will have to umount your FS before to
set the largefile,
unless you have the Online JFS product installed
(with the correct level of patch).

Regards.

[MANOJ SRIVASTAVA]

Hi Tarek


Incase you donot have ONLINE JFS installed you will have to unmount the file system and then do the fsadm on the raw lvol .


few other tips

mkfs -m < file system name > will tell you what the options were used to create the filesystem

ofcourse you know the command to set to the largefiles option.


Manoj Srivastava