Maximum value for ulimit SCO OpenServer 5.0.6

[thegress]

Greetings,

Last night our system tried to write a file greater
than 2 Gig. At first I thought this would not be
a problem for I would just increase 'ulimit' and
relink the Kernel. However, 2 Gig is the maximum
recommended size. I did a quick search on the Net
and could not find any info except 2 Gig seems to be the limit. The config utility did ask me if I wanted to override the recommended limit/range...but, I chickened out. Does anyone know if I can safely exceed this limit?

 

[PHV]

2 Gig is the limit, even for 5.0.7

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[stanhubble]

depends on the filesystem. there are no native filesystems that sco uses that supports > 2GB files.
an NFS mount may work if the NFS server supports a ulimit that large. you also may run into problems with local utilities that assume a 2GB max file size.

legend / 5.0.8 / 6 is supposed to have this ability i think.

 

[cdlvj]

SCO OpenServer file systems and characterics

The EAFS (Extended Acer Fast Filesystem) is the default filesystem used by SCO UNIX Operating System Versions 2.0 and 3.0, and is also the default filesystem for the boot filesystem (/stand) on SCO OpenServer products.


* Uses checkpointing and intent logging.
* Supports long filenames and symbolic links.
* Has 65,488 inodes per filesystem (less than 2^16).
* Has a 2GB maximum for file and filesystem size.
* Uses 1KB logical data blocks.
* Is a bootable filesystem and is used when creating the boot filesystem.


The HTFS (High Throughput Filesystem) is a new filesystem for SCO OpenServer systems. It transparently provides significant performance improvement by using caching to increase data throughput. This is the default filesystem for the SCO OpenServer Host and Enterprise.

* Uses checkpointing. The filesystem is marked clean at regular intervals. If a filesystem is marked clean when the system halts, it may not be necessary for it to be checked by fsck(ADM).
* Uses intent logging. The filesystem transactions are recorded in a log and then committed to disk. This increases system recovery speed with a very small performance penalty. Intent logging works in tandem with checkpointing
* Uses versioning to allow users to undelete a file.
* Supports long filenames and symbolic links.
* Has a maximum 134,000,000 inodes per filesystem.
* Has a maximum file size of 2GB and a maximum filesystem
size of 1 terabyte.
* Has a logical data block of 1KB.
* Is not a bootable filesystem.


The DTFS (Desktop Filesystem) is designed for use on laptop, desktop, and notebook computers. This is the default filesystem for the SCO OpenServer Desktop product.

* Uses transparent data compression and a more efficient disk media format to increase the storage capacity of your disks.
* Supports long names and symbolic links.
* Can contain either user data or an inode on any block on the disk. The number of inodes in the filesystem can grow as necessary and is limited to the size of the partition.
* Has a maximum file size of 2GB and a maximum filesystem size of 1 terabyte.
* Uses a variable block size that is a multiple of 512 bytes up to 4KB. This helps minimize wasted space at the end of incomplete blocks.
* Is not a bootable filesystem.


Other filesystems that are supported by SCO are included in the following list. Note that support for the AFS and S51K filesystems are installed by default and do not need to be linked into the kernel.

* AFS (Acer Fast Filesystem)
* S51K Filesystem.
* High Sierra/ISO9660/Rockridge CD-ROM Filesystem.
* DOS Filesystem.
* NFS (Network Filesystem)
* NUCFS (NetWare for UNIX Clients Filesystem)
* LMCFS (LAN Manager Client Filesystem)
* XENIX