largefiles option missing in fstab

[Gordana]

Hello,

I have a question about filesystems on HP-UX 11.11. After creating filesystem with ‘largefiles’ option everything on the screen looks Ok but /etc/fstab is not showing ‘largefiles’. Have I done something wrong? Missed any steps?

Create Logical volume:

# lvcreate -L 130000 -n cucc2data vg05
Logical volume "/dev/vg05/cucc2data" has been successfully created with
character device "/dev/vg05/rcucc2data".
Logical volume "/dev/vg05/cucc2data" has been successfully extended.
Volume Group configuration for /dev/vg05 has been saved in /etc/lvmconf/vg05.conf

Create filesystem with largefilesystem option:
# newfs -F vxfs -o largefiles /dev/vg05/rcucc2data
version 4 layout
133120000 sectors, 16640000 blocks of size 8192, log size 256 blocks unlimited inodes, largefiles supported
16640000 data blocks, 16639080 free data blocks
508 allocation units of 32768 blocks, 32768 data blocks
last allocation unit has 26624 data blocks

Verify filesystem:

# mkfs -F vxfs -m /dev/vg05/rcucc2data
mkfs -F vxfs -o ninode=unlimited,bsize=8192,version=4,inosize=256,logsize=256,largefiles /dev/vg05/rcucc2data 133120000

# fsadm /cucc2data
fsadm: /etc/default/fs is used for determining the file system type
largefiles

Mount newly created filesystem:

# cd /
# mkdir /cucc2data
# mount /dev/vg05/cucc2data /cucc2data
# bdf | grep cucc2data
/dev/vg05/cucc2data
133120000 60754280 71800408 46% /cucc2data

Update /etc/fstab file:

# cp fstab fstab.13012009
# mount -p > /etc/fstab
# more fstab
/dev/vg00/lvol3 / hfs defaults 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 0
/dev/vg01/lvol3 /work_ftp vxfs log,largefiles 0 0
/dev/vg00/lvol7 /var hfs defaults 0 0
/dev/vg00/lvol10 /var/adm/sw hfs defaults 0 0
/dev/vg00/lvol9 /var/adm/crash hfs defaults 0 0
/dev/vg00/lvol6 /usr hfs defaults 0 0
/dev/vg04/lvol2 /unicenter vxfs log,largefiles 0 0
/dev/vg00/lvol5 /tmp hfs defaults 0 0
/dev/vg00/lvol14 /tivoli vxfs delaylog,largefiles 0 0
/dev/vg00/lvol12 /stand2 hfs largefiles 0 0
/dev/vg04/lvol1 /software vxfs log,largefiles 0 0
/dev/vg02/lvol1 /relay vxfs log,largefiles 0 0
/dev/vg00/lvol11 /prod_data vxfs delaylog,largefiles 0 0
/dev/vg00/lvol13 /patches vxfs delaylog,largefiles 0 0
/dev/vg00/lvol4 /opt hfs defaults 0 0
/dev/vg03/lvol1 /nbapp vxfs log,largefiles 0 0
/dev/vg00/lvol15 /logs vxfs delaylog,largefiles 0 0
/dev/vg00/lvol8 /home hfs defaults 0 0
/dev/vg01/lvol6 /data2 vxfs delaylog,largefiles 0 0
/dev/vg01/lvol5 /cucc3 vxfs log,largefiles 0 0
/dev/vg02/lvol2 /cucc2 vxfs log,largefiles 0 0
/dev/vg01/lvol1 /cucc vxfs log,largefiles 0 0
/dev/vg01/lvol2 /bank_cgi vxfs log,largefiles 0 0
/dev/vg05/cucc2data /cucc2data vxfs log 0 0

Why I am missing attribute “largefiles” for cucc2data in /etc/fstab?

Thanks in advance for all help.

[James R. Ferguson · Accepted solution]

Hi:

The 'largefiles' or 'nolargefiles' option as placed in '/etc/fstab' _only_ tells you the intention at mount-time. That is, if 'nolargefiles' is set there, and you try to mount a fileystem with a 'largefiles' bit set, the mount fails.

You can add the setting as a doumentary thing if you want, but it's the underlying filesystem setting that matters. Using the 'mkfs -m' to test an easy verification.

Regards!

...JRF...

[Gordana]

So I don't have a reason to panic. At least for now :)

Here is verification:

# mkfs -m /dev/vg05/cucc2data
mkfs -F vxfs -o ninode=unlimited,bsize=8192,version=4,inosize=256,logsize=256,largefiles /dev/vg05/cucc2data 133120000




Thank you James very much.

[Tingli]

Very often the file system is created in SAM, which is defaulted as no large file system. It needs backup and restore the whole file system to change it to large file system. If there is Online JFS, you can change large file system to non-large file system on the fly.

[Gordana]

Tingli,

Thank you for additional information.

I wanted 'largefiles' option and I was using command line to create that filesystem. As James explained, everything is in order.

[Dennis Handly]

>Tingli: It needs backup and restore the whole file system to change it to large file system. If there is Online JFS ...

This is not true. You don't need Online JFS (or umount) to change to large files. Just:
fsadm -F vxfs -o largefiles device

[Gordana]

Thank you for all responses.

[Gokul Chandola]

Hi,
You can use SAM for that, or if large file supported then you manually Enter in fstab file. It will auto sync when system will restart.

Regards,
Gokul Chandola