| AdvFS | |
| Full Name: | Tru64 UNIX Advanced File System |
| Introduction Os: | OSF/1 |
| Bad Blocks Struct: | Table |
| Max Filename Size: | 255 bytes |
| Os: | Tru64 UNIX |
AdvFS, also known as Tru64 UNIX Advanced File System, is a file system developed in the late 1980s to mid-1990s[1] by Digital Equipment Corporation for their OSF/1 version of the Unix operating system (later Digital UNIX/Tru64 UNIX).[2] In June 2008, it was released as free software under the GPL-2.0-only license.[3] AdvFS has been used in high-availability systems where fast recovery from downtime is essential.[4]
AdvFS uses a relatively advanced concept of a storage pool (called a file domain) and of logical file systems (called file sets). A file domain is composed of any number of block devices, which could be partitions, LVM or LSM devices. A file set is a logical file system created in a single file domain. Administrators can add or remove volumes from an active file domain, providing that there is enough space on the remaining file domain, in case of removal. This was one of the trickier original features to implement because all data or metadata residing on the disk being removed had to first be migrated, online, to other disks, prior to removal.
File sets can be balanced, meaning that file content of file sets be balanced across physical volumes. Particular files in a file set can be striped across available volumes.
Administrators can take a snapshot (or clone) of any active or inactive file set. This allows for easy on-line backups and editing.
Another feature allows administrators to add or remove block devices from a file domain, while the file domain has active users. This add/remove feature allows migration to larger devices or migration from potentially failing hardware without a system shutdown.
Its features include:
Under Linux, AdvFS supports an additional ‘’syncv’’ system call to atomically commit changes to multiple files.[6]
AdvFS, also known as Tru64 UNIX Advanced File System, was developed by Digital Equipment Corporation engineers in the late 1980s to mid-1990s[1] in Bellevue, WA (DECwest). They had previously worked on the earlier (cancelled) MICA and OZIX projects there.
It was first delivered on the DEC OSF/1 system (later Digital UNIX/Tru64 UNIX). Over time, development moved to teams located in Bellevue, WA and Nashua, NH. Versions were always one version number behind the operating system version. Thus, DEC OSF/1 v3.2 had AdvFS v2.x, Digital UNIX 4.0 had AdvFS v3.x and Tru64 UNIX 5.x had AdvFS v4.x. It is generally considered that only AdvFS v4 had matured to production level stability, with a sufficient set of tools to get administrators out of any kind of trouble. The original team had enough confidence in its log based recovery to release it without an "fsck" style recovery utility on the assumption that the file system journal would always be allocated on mirrored drives.
In 1996, Lee and Thekkath[7] described the use of AdvFS on top of a novel disk virtualisation layer known as Petal. In a later paper,[8] Thekkath et al. describe their own file system (Frangipani) built on top of Petal and compare it to the performance of AdvFS running on the same storage layer.
Shapiro and Miller[9] compared the performance of files stored in AdvFS to Oracle RDBMS version 7.3.4 BLOB storage.
Compaq Sierra Parallel File System (PFS) created a cluster file system based on multiple local AdvFS filesystems; testing carried out at Lawrence Livermore National Laboratory (LLNL) in 2000–2001 found that while the underlying AdvFS filesystem had adequate performance (albeit with high CPU utilisation), the PFS clustering layer on top of it performed poorly.[10]
On June 23, 2008, its source code was released by Hewlett-Packard[3] under the GPL-2.0-only license (instead of the recently released GPLv3) at SourceForge in order to be compatible with the also GPL-2.0-only licensed Linux kernel.[11]