Technical article 105852

What are the filesystem types that can be used in SCO OpenServer 5?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

What are the filesystem types and the corresponding limitation sizes that can be used in SCO OpenServer 5?

Solution

Filesystem types differ in capabilities that may affect how they are used.

The supported disk filesystems are the following:

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

The following is a summary of the supported filesystem types:

                                      Check-    Intent
Filesystem | Bootable | Versioning | pointing | logging | Advantages
-----------|----------|------------|----------|---------|---------------------
           |          |            |          |         | Backwards
AFS        |   X      |            |    X     |    X    | compatibility
-----------|----------|------------|----------|---------|---------------------
           |          |            |          |         | Used to create
EAFS       |   X      |            |    X     |    X    | boot filesystem
-----------|----------|------------|----------|---------|---------------------
           |          |            |          |         | Uses data compression
DTFS       |          |     X      |    X     |    X    | to save disk space
-----------|----------|------------|----------|---------|---------------------
           |          |            |          |         | Defaults use caching
HTFS       |          |     X      |    X     |    X    | for high performance
-----------|----------|------------|----------|---------|---------------------
           |          |            |          |         | Backwards
S51K       |   X      |            |    X     |         | compatibility
-----------|----------|------------|----------|---------|---------------------
           |          |            |          |         | Backwards
XENIX      |   X      |            |          |         | compatibility
-----------|----------|------------|----------|---------|---------------------
           |          |            |          |         | Eliminate need
DOS        |          |            |          |         | for DOS utilities
-----------|----------|------------|----------|---------|---------------------
NOTE:     Checkpointing
          -------------
          Checkpointing is the process of transitioning filesystems to a clean
          state when the filesystem is inactive.  Filesystem data consists of
          user file data and "metadata" (data which refers to accounting info
          used internally by the filesystem to represent a file).

By default, HTFS, EAFS, AFS and S51K filesystems periodically checkpoint (write) cached metadata back to the disk. This increases the probability that the filesystem metadata is in a consistent state if the system is halted unexpectedly.

For the root filesystem, the kernel parameter ROOTCHKPT controls
this feature.  If overhead is an issue, disable checkpointing by
setting ROOTCHKPT to 0.

For non-root filesystems, to disable checkpointing see the /etc/default/filesys file.

NOTE:     Intent Logging
          --------------
          This minimises system downtime. It does not increase the reliability
          of the filesystem.  When the system is halted unexpectedly, instead
          of the fsck command checking entire filesystem, it only checks
          logged transactions.
A log file is created as a special file in the root of each mounted
filesystem.  This file is hidden.  If logging is disabled the log
file appears as .ilog0000.

Intent logging is enabled by default for the HTFS, DTFS, AFS & EAFS filesystems.

For the root filesystem, the kernel parameter ROOTLOG controls this feature.

If overhead is an issue, disable intent logging by setting ROOTLOG to 0.

For non-root filesystems, to disable intent logging see the /etc/default/filesys file.

NOTE:     Versioning
          ----------
          For HTFS and DTFS there is the ability to apply versioning to your
          filesystem to prevent the deletion of files.  This will, though,
          apply an overhead to your performance.

Versioning allows you to recover deleted files with the "undelete" command.

It applies only to DTFS and HTFS filesystems and is not configured by default.

To apply it run:
scoadmin | H/W / Kernel Manager
Tune Params
10 - Filesystem Config
For Non-Root Filesystems, set the MAXVDEPTH kernel param to the
desired no. of undeletable (versioned) files allowed.  The max is
65535. 0 means disabled versioning.
Set the MINVTIME to the desired number of secs before a file is
versioned.  Default is 0.

For root filesystems set ROOTMAXVDEPTH and ROOTMINVTIME.

This will then relink the Kernel and re-build the Unix environment.

The changes will take effect when you next boot your server.

See also

man fstyp(ADM), man mkfs(ADM).

ta104467, "Disk drive capacity and filesystem limitations under SCO UNIX 3.2 Version 4.x."

From the Xinuos technical article database, record 105852. Reproduced with permission. The original is at www.sco.com/ta/105852, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.