User cannot create file over 25G ?

[Jerry_109]

HP-UX B.11.11 U 9000/800 :

Hello All,

I have user that cannot create a file over 25G on the following lv or there any limitations I can change ? :

# bdf .
Filesystem kbytes used avail %used Mounted on
/dev/vg01/dbarchive
102432768 27878136 73972336 27% /dbarchive

######################################
root@hohp112:

# fstyp -v /dev/vg01/dbarchive
vxfs
version: 4
f_bsize: 8192
f_frsize: 8192
f_blocks: 12804096
f_bfree: 9319329
f_bavail: 9319329
f_files: 800
f_ffree: 2139030368
f_favail: 2139030368
f_fsid: 1073807369
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 7
f_size: 12804096

#################################

[Patrick Wallek · Accepted solution]

How is the user trying to create the file? What tools/utilities are in use? What error does the user receive?

[NMory]

Limitation is 2GB file size...I am not mistaken.

NM

[Steven E. Protter]

Shalom,

If largefiles is enabled the limit after 2 GB is 128 TB.

If I'm not mistaken.

25 GB is not significant.

Check for quotas, its possible to impose them in HP-UX and if not that limitations of the tool the user is using.

SEP

[Steven E. Protter]

Forgot something Jerry.

Check kmtune/kctune output.

There may be a kernel limitation coming to play.

SEP

[Jerry_109]

How do you check if largefiles are enabled ?

[NMory]

#fsadm -F vxfs /

NM

[NMory]

To rutn it on:

/usr/sbin/fsadm -F vxfs -o largefiles /dev/vg0#/rlvol#

NM

[Marco A.]

In order to create large files (> 4G) on HP-UX system, a HFS file system must be enabled to contain large files. That can be accomplished by the following steps:

Unmount the volume.

/usr/sbin/umount

ex: /usr/sbin/umount /newdisk

Configure it to contain large files.

fsadm -F hfs -o largefiles

ex: fsadm -F hfs -o largefiles /dev/vg00/lvol1

Mount it back to be able to create large files.

/usr/sbin/mount -F hfs -o largefiles

ex: /usr/sbin/mount -F hfs -o largefiles /dev/vg00/lvol1 /newdisk

Hope this helps,

MArc0

[NMory]

Another way

#fstyp -v /dev/vg0#/lvol#

f_flag: 16 = largefiles
f_flag: 0 = no_largefiles

NM

[Jerry_109]

root@hohp112[/root]
# fsadm -F vxfs /dbarchive
largefiles

[Jerry_109]

# kmtune | egrep -i "file|siz"
bcvmap_size_factor 2 - 2
eqmemsize 15 - 15
file_pad - - 10
iomemsize - - 40000
maxdsiz 0x10000000 - 0x10000000
maxdsiz_64bit 1900000000 - 1900000000
maxfiles 2896 - 2896
maxfiles_lim 2048 Y 2048
maxssiz 0x800000 - 0X800000
maxssiz_64bit 0x800000 - 0X800000
maxtsiz 0x4000000 Y 0X4000000
maxtsiz_64bit 0x40000000 Y 0X40000000
ncsize 13230 - (NINODE+VX_NCSIZE)+(8*DNLC_HASH_LOCKS)
nfile 32439 - 32439
sendfile_max 0 - 0
vol_dcm_replay_size 262144 - (256*1024)
vol_maxstablebufsize 256 - 256
volcvm_cluster_size 16 - 16
voliomem_chunk_size 65536 - (64*1024)
vps_pagesize 4 - 4
vx_ncsize 1024 - 1024

[Marco A.]

The parameters have preâ defined defaults, but can be reconfigured in the kernel.

Some may need to be adjusted when swap space is increased.
This is discussed in more detail in the section on configuring the HPâ UX kernel. Swap 6 HP Global Technical Partner â Cadence bufpages create_fastlinks fs_async hpux_aes_override maxdsiz maxfiles maxfiles_lim maxssiz maxswapchunks maxtsiz maxuprc netmemmax nfile ninode nproc npty Sets number of buffer pages Store symbolic link data in the inode Sets asynchronous write to disk Controls directory creation on automounted disk drives Limits the size of the data segment...

Check for those kernel parameters, mainly the maxfiles , and maxfiles_lim.

Hope this helps,

Marc0

[Patrick Wallek]

OK, I'll ask again ---

How is the user trying to create the file? What tools/utilities are in use? What error does the user receive?

[Marco A.]

or maybe the application that you are using is limiting the file size, this because it really has large files enabled.

Marc0

[Jerry_109]

User error :

SQL2419N The target disk disk has become
full.
Explanation: During the processing of a
database utility, the target disk became full. The
utility has stopped and the target is deleted.
User Response: Ensure enough disk space is
available for the utility or direct the target to
other media, such as tape.
On unix-based systems, this disk full condition
may be due to exceeding the maximum file size
allowed for the current userid. Use the chuser
command to update fsize. A reboot may be
necessary.

[Patrick Wallek]

OK, so this is a SQL error. Is this from Oracle? some other database? What was the command that generated this error?

[Jerry_109]

Patrick,

I'm waiting for response from user. They use IBM DB2.

[Marco A.]

well, at least now we know that is not a problem of the OS as well!...

[A. Clay Stephenson]

maxfiles or maxfiles_lim have nothing to do with this. There are only a few things at the system level which can cause this:

1) Insufficient free space in the file system -- which doesn't appear to be the case.
2) Reaching ulimit for the process. Before the user starts the application, have him do a "ulimit -Hf" and a "ulimit -Sf" to show the Hard and Soft file size limits.
3) Quotas -- Do you have quotas enabled fore this file system?

This will only take you so far because the last ulimit wins. It is possible that the application itself does a ulimit and reduces the value -- not likely but possible. There could also be a limit imposed by the application itself (e.g in a confuration file).

I would attach tusc to the application and you should be able to see the problem when write() or lseek() fails. Posting that output should tremendously narrow the problem.

[Jerry_109]

Sorry all,

I just got out of a meeting :

# grep scifudbp /etc/passwd
scifudbp:xxxxxxxxxxx:22700:5111:powercom,unix,ho,:/u00/scifudbp:/usr/bin/sh

root@hohp112[/backup]
# su - scifudbp

$MYHOST PATH=$PWD ($USER)
=> ulimit -Hf
unlimited

$MYHOST PATH=$PWD ($USER)
=> ulimit -Sf
unlimited

$MYHOST PATH=$PWD ($USER)
=> ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 262144
stack(kbytes) 8192
memory(kbytes) unlimited
coredump(blocks) 4194303
nofiles(descriptors) 2896

$MYHOST PATH=$PWD ($USER)