Automatic Drive Cleaning #218, Cleanup by Dataclass #391

Contents of Version 4.1

OPERATING SYSTEMS

•Initial release of FileServ on IRIX 6.5.6.

•Support for Solaris 2.6 has been put back in FileServ.

NEW DRIVE SUPPORT

•Additional drives supported by this release of FileServ include the following:

-Fujitsu M8100. Configure this drive as an IBM 3590B1A.

-Quantum DLT 8000. Configure this drive as a Quantum DLT 4000.

AUTOMATIC DRIVE CLEANING (#218)

•Automatic drive cleaning has been added for the following drives:

-Sony AIT-1 SDX-300 and AIT-2 SDX-500.

-Quantum DLT 4000, DLT 7000, and DLT 8000.

-IBM 3590B1A and 3590E1A.

After upgrading, you must import media into the FX_mediatype_clean class, where FX is the fileserv id and mediatype is specific media, such as 8590.

REMOVE DATABASE INFORMATION (#397)

•A new -cclassname option has been added to the fsclean command. The clean operation will be performed on media that belongs to the DataClass specified by classname. The fsclean command removes information from the trashcan (database) for deleted files.

CLEANUP BY DATACLASS (#391)

•A new -cclass option for cleanup (truncate) policies has been added to the fspolicy -tcommand. The -c class option allows you to specify a DataClass to be invoked with the cleanup policy.

IMPROVE PERFORMANCE (#382)

•All commands that map a file system or database have been modified to reduce memory requirements and hence improve performance. These commands include fspolicy (#398), fsaudit, fsdump, and fsaddrelation. A new set of directories will be created under

$FS_HOME/internal/mapping_dir/dev_key.#, where # is an internal number assigned by

FileServ. The space required for the mapping files on disk is about 100 bytes per file and about 120 bytes per directory for all files managed by FileServ. For example, a file system with 100,000 files and 5,000 directories, requires about 10.6Mb of space for the mapping files.

Page 18 of 22

FileServ Version 4.3—600726 Rev A