Technical article 105249

What is the .ilog0000 file for?

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

What is the /.ilog file for?  Some 3rd party backup utilities may
not be able to backup or restore this file.

Cause

.ilog0000 is a special file used by the intent logging system
available under SCO OpenServer 5 and later releases.  If you
do a `ls -al /.ilog0000` you will see this:
----------   1 root     60007      10240 Jun  1 12:46 .ilog0000

Solution

Messages from backup utilities about being unable to extract this file can be safely ignored.

Intent logging minimizes system downtime after abnormal shutdowns
by logging filesystem transactions.  When the system is halted
unexpectedly, this log can be replayed automatically, and outstanding            filesystem transactions are then completed.  The check and repair time           for filesystems can thereby be reduced to a few seconds, regardless of           the filesystem size.
The ability to locate and check only affected areas of the disk
for inconsistencies is central to the logging mechanism.  The
structure of the mechanism is:
-- A log file is created as a special file in the root of each
mounted filesystem.  (This file is normally invisible and is
neither readable nor removable when logging is enabled.  When
logging is disabled on a previously enabled filesystem, the
log file appears as .ilog0000.)

-- The location of the file is kept in the superblock (an area at the top of the filesystem structure which describes the attributes of the filesystem in terms of type, size, available space and latest modification time).

-- Changes to a file's meta data (as opposed to the data it
contains) such as inodes and block bitmaps are cached in memory.
Before making any changes on disk, a log entry is written
synchronously.  After the changes are performed, a ``transaction
complete'' indication is stored on disk.
If the system crashes before the log is written, it is as if the
change (any modifications to the filesystem) never occurred.  If
the system crashes after the log is written, but before the
transaction complete, fsck either completes the change or undoes
it. If the system crashes after the transaction is completed,
then the modification has been completed, and there is nothing
for fsck to do.
NOTE:     For optimum benefit, both logging and checkpointing should be
          enabled.  Checkpointing marks the filesystem as clean whenever
          the filesystem is inactive.  If the system needs to be checked
          (in the event of an abnormal system halt, for instance) only areas
          of the disk manipulated since the last checkpoint operation need
          to be examined for inconsistencies.

See also

System Administration Guide Chapter 2, Administering Filesystems.

From the Xinuos technical article database, record 105249. Reproduced with permission. The original is at www.sco.com/ta/105249, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

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.