AdvFS, also known as Tru64 UNIX Advanced File System, is a file system developed in the late 1980s to mid-1990s by Digital Equipment Corporation for their OSF/1 version of the Unix operating system (later Digital UNIX/Tru64 UNIX). In June 2008, it was released as free software under the GNU GPLv2 license. AdvFS has been used in high-availability systems where fast recovery from downtime is essential.:428
|Developer(s)||Digital Equipment Corporation|
|Full name||Tru64 UNIX Advanced File System|
|Introduced||1993 with OSF/1|
|Max. volume size||16 TiB|
|Max. file size||16 TiB|
|Max. filename length||255 bytes|
|Supported operating systems||Tru64 UNIX|
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.
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:
- a journal to allow for fast crash recovery
- undeletion support
- high performance
- dynamic structure that allows an administrator to manage the file system on the fly
- on the fly creation of snapshots
- defragmentation while the domain has active users
AdvFS, also known as Tru64 UNIX Advanced File System, was developed by Digital Equipment Corporation engineers in the late 1980s to mid-1990s 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 described the use of AdvFS on top of a novel disk virtualisation layer known as Petal. In a later paper, 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.
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.
On June 23, 2008, its source code was released by Hewlett-Packard under GNU General Public License version 2 (instead of the recently released GPLv3) at SourceForge in order to be compatible with the also GPLv2 licensed Linux kernel license.
- "Revision history?". SourceForge.net. Retrieved 2008-06-25.
- Steven M. Hancock (January 2001). Tru64 Unix File System Administration Handbook. Digital Press. p. 258. ISBN 978-1-55558-227-2.
- Press release concerning the release of the AdvFS source code
- Brady, Don. Designing GIS for high availability and high performance. High Performance Computing in the Asia-Pacific Region, 2000. Proceedings. The Fourth International Conference/Exhibition on. pp. 423–431. doi:10.1109/HPC.2000.846591.
AdvFS is a journaled, local file system that provides higher availability, and greater flexibility and recovery than traditional UNIX file systems. The recovery takes just a few seconds for AdvFS...
- Amir H. Majidimehr (1996). Optimizing UNIX for Performance. Prentice Hall PTR. p. 69. ISBN 978-0-13-111551-4.
Log-structured file system implementations include the AIX Journalled File System (JFS), the DEC Advanced File System (AdvFS), and the SUN UFS with Transaction Logging in Solaris DiskSuite.
- Verma, Rajat, et al. "Failure-atomic updates of application data in a Linux file system.” 13th USENIX Conference on File and Storage Technologies (FAST 15). 2015. online version
- Lee, Edward K., and Chandramohan A. Thekkath. "Petal: Distributed virtual disks." ACM SIGPLAN Notices. Vol. 31. No. 9. ACM, 1996. Available online
- Chandramohan A. Thekkath, Timothy Mann, and Edward K. Lee. 1997. Frangipani: a scalable distributed file system. SIGOPS Oper. Syst. Rev. 31, 5 (October 1997), 224-237. Also in: Chandramohan A. Thekkath, Timothy Mann, and Edward K. Lee. 1997. Frangipani: a scalable distributed file system. In Proceedings of the sixteenth ACM symposium on Operating systems principles (SOSP '97), William M. Waite (Ed.). ACM, New York, NY, USA, 224-237. Online version
- Shapiro, Michael, and Ethan Miller. "Managing databases with binary large objects." Mass Storage Systems, 1999. 16th IEEE Symposium on. IEEE, 1999. Available online
- Uselton, A C. The Performance of PFS, the Compaq Sierra Product’s Parallel File System. United States: N. p., 2001. Web. doi:10.2172/15006183. Available online
- Linus Torvalds (2000-09-08). "Linux-2.4.0-test8". lkml.iu.edu. Retrieved 2015-11-21.
The only one of any note that I'd like to point out directly is the clarification in the COPYING file, making it clear that it's only _that_particular version of the GPL that is valid for the kernel. This should not come as any surprise, as that's the same license that has been there since 0.12 or so, but I thought I'd make that explicit
- Source code at Sourceforge.net