LDP
/
old-www
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
old-www/HOWTO/Filesystems-HOWTO-9.html

853 lines
33 KiB
HTML
Raw Permalink Blame History

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
<TITLE>Filesystems HOWTO: Other filesystems</TITLE>
<LINK HREF="Filesystems-HOWTO-10.html" REL=next>
<LINK HREF="Filesystems-HOWTO-8.html" REL=previous>
<LINK HREF="Filesystems-HOWTO.html#toc9" REL=contents>
</HEAD>
<BODY>
<A HREF="Filesystems-HOWTO-10.html">Next</A>
<A HREF="Filesystems-HOWTO-8.html">Previous</A>
<A HREF="Filesystems-HOWTO.html#toc9">Contents</A>
<HR>
<H2><A NAME="s9">9.</A> <A HREF="Filesystems-HOWTO.html#toc9">Other filesystems</A></H2>
<H2><A NAME="ss9.1">9.1</A> <A HREF="Filesystems-HOWTO.html#toc9.1">ADFS - Acorn Disc File System </A>
</H2>
<P>The Acorn Disc Filing System is the standard filesystem of the
RiscOS operating system which runs on Acorn's ARM-based Risc PC
systems and the Acorn Archimedes range of machines. </P>
<P>Linux kernel 2.1.x+ supports this filesystem. Author of Linux filesystem
implementation is Russell King &lt;
<A HREF="mailto:rmk@arm.uk.linux.org">rmk@arm.uk.linux.org</A>&gt;.</P>
<H2><A NAME="affs"></A> <A NAME="ss9.2">9.2</A> <A HREF="Filesystems-HOWTO.html#toc9.2">AFFS - Amiga fast filesystem</A>
</H2>
<P>The Fast File System (FFS) is the common filesystem used on hard
disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20).</P>
<P>Linux kernel 2.1.x+ supports this filesystem. Author of Linux filesystem
implementation is Ray Burr &lt;
<A HREF="mailto:ryb@nightmare.com">ryb@nightmare.com</A>&gt;.</P>
<H2><A NAME="befs"></A> <A NAME="ss9.3">9.3</A> <A HREF="Filesystems-HOWTO.html#toc9.3">BeFS - BeOS filesystem</A>
</H2>
<P>BeFS is
<A HREF="Filesystems-HOWTO-1.html#journal">journaling</A> filesystem used in BeOS.
For more information about BeFS see
<A HREF="http://www.mkp.com/books_catalog/1-55860-497-9.asp">Practical File System Design with the Be File System</A>
book or BeFS linux driver source code.</P>
<P>Linux BeFS implementation:
<A NAME="befs_linux"></A> </P>
<P>
<UL>
<LI> Homepage:
<A HREF="http://hp.vector.co.jp/authors/VA008030/bfs/">http://hp.vector.co.jp/authors/VA008030/bfs/</A></LI>
<LI> Download:
<A HREF="http://hp.vector.co.jp/authors/VA008030/bfs/bfs-19990528.tar.gz">http://hp.vector.co.jp/authors/VA008030/bfs/bfs-19990528.tar.gz</A></LI>
<LI> Author: Makoto Kato &lt;
<A HREF="mailto:m_kato@ga2.so-net.ne.jp">m_kato@ga2.so-net.ne.jp</A>&gt;</LI>
<LI> Access: Read-only</LI>
<LI> License: GPL</LI>
</UL>
This driver supports x86 and PowerPC Linux platform.
Also, it only supports readable in hard disk and floppy disk.</P>
<H2><A NAME="bfs"></A> <A NAME="ss9.4">9.4</A> <A HREF="Filesystems-HOWTO.html#toc9.4">BFS - UnixWare Boot Filesystem</A>
</H2>
<P>UnixWare BFS filesystem type is a special-purpose filesystem. It was designed
for loading and booting UnixWare kernel. BFS was designed as a
<A HREF="Filesystems-HOWTO-1.html#contiguous">contiguous filesystem</A>. BFS supports only one
(root) directory and you can create only regular files; no subdirs or
special files such as devices or sockets can be created.</P>
<P>For more information about BFS see
<A HREF="http://uw7doc.sco.com/FS_admin/_The_bfs_File_System_Type.html">http://uw7doc.sco.com/FS_admin/_The_bfs_File_System_Type.html</A>.
<UL>
<LI>
<A HREF="http://uw7doc.sco.com/FS_admin/_The_bfs_Superblock.html">http://uw7doc.sco.com/FS_admin/_The_bfs_Superblock.html</A>
- superblock</LI>
<LI>
<A HREF="http://uw7doc.sco.com/FS_admin/_bfs_Inodes.html">http://uw7doc.sco.com/FS_admin/_bfs_Inodes.html</A>
- inodes</LI>
<LI>
<A HREF="http://uw7doc.sco.com/FS_admin/_bfs_Storage_Blocks.html">http://uw7doc.sco.com/FS_admin/_bfs_Storage_Blocks.html</A>
- storage blocks</LI>
</UL>
</P>
<P>You can access BFS filesystem from Linux:
<A NAME="bfs_linux"></A>
<UL>
<LI> Homepage:
<A HREF="http://www.ocston.org/~tigran/patches/bfs/">http://www.ocston.org/~tigran/patches/bfs/</A></LI>
<LI> Download: In the Linux kernel, patches available at homepage.</LI>
<LI> Author: Tigran A. Aivazian &lt;
<A HREF="mailto:tigran@ocston.org">tigran@ocston.org</A>&gt;</LI>
<LI> License: GPL</LI>
<LI> Access: Read/write (write part is limited, no compactification yet)</LI>
</UL>
The support for BFS is included in the Linux
kernel since version 2.3.25. If you are using an earlier
kernel, check if BFS homepage contains a patch which adds
support for this filesystem. The homepage also contains
bugfixes/enhancement which are not yet merged into the
official kernel.</P>
<P>There is also mine old implementation, which is now obsolete. My
plan is to port this code to FreeBSD:</P>
<P>
<A NAME="bfs_linux_old"></A>
<UL>
<LI> Homepage:
<A HREF="http://www.penguin.cz/~mhi/fs/bfs/">http://www.penguin.cz/~mhi/fs/bfs/</A></LI>
<LI> Download:
<A HREF="ftp://ftp.penguin.cz/pub/users/mhi/bfs/">ftp://ftp.penguin.cz/pub/users/mhi/bfs/</A></LI>
<LI> Author: Martin Hinner &lt;
<A HREF="mailto:mhi@penguin.cz">mhi@penguin.cz</A>&gt;</LI>
<LI> License: GPL</LI>
<LI> Access: Read-only</LI>
</UL>
This is read-only UnixWare Boot filesystem support for Linux. You can use
it to mount read-only your UnixWare /stand partition or floppy disks. I don't
plan a read-write version, but if you want it mail me. You might be also
interested in
<A HREF="#vxfs">VxFS</A> Linux support.</P>
<H2><A NAME="ss9.5">9.5</A> <A HREF="Filesystems-HOWTO.html#toc9.5">CrosStor filesystem</A>
</H2>
<P>This is new name for <B>High throughput filesystem (HTFS)</B>. For more
information see CrosStor homepage at
<A HREF="http://www.crosstor.com">http://www.crosstor.com</A>.</P>
<H2><A NAME="dtfs"></A> <A NAME="ss9.6">9.6</A> <A HREF="Filesystems-HOWTO.html#toc9.6">DTFS - Desktop filesystem</A>
</H2>
<P>Goals in designing the Desktop File System were influenced by impression of
what environment was like for small computer systems. DTFS compress the data
stored in regular files to reduce disk space requirements (directories remain
uncompressed). Compression is performed a page at a time and occur 'on-the-fly'.
DTFS supports LZW and no-compression but you can add your own algorithms. Some
space is saved by not pre-allocating inodes. Any disk block is fair game
to be allocated as an inode. Each inode is stored as a B+tree. For more
information see DTFS USENIX paper
(you can download it from
<A HREF="ftp://ftp.crosstor.com/pub/DTFS/papers/">ftp://ftp.crosstor.com/pub/DTFS/papers/</A>).</P>
<P>Read/Write <B>commercial</B> driver available from CrosStor for UnixWare
and SUN Solaris:</P>
<P>
<A NAME="dtfs_unixware"></A> </P>
<P>
<UL>
<LI> Download:
<A HREF="ftp://ftp.crosstor.com/pub/DTFS/">ftp://ftp.crosstor.com/pub/DTFS/</A></LI>
<LI> License: Commercial?</LI>
<LI> Access: Read/Write</LI>
</UL>
</P>
<H2><A NAME="enhfs"></A> <A NAME="ss9.7">9.7</A> <A HREF="Filesystems-HOWTO.html#toc9.7">EFS - Enhanced filesystem (Linux)</A>
</H2>
<P>The Enhanced Filing system project aims to create a new
filing system for Linux and eventually other OSs which will allow the administrator
to define mountable "file systems" on a set of block devices (either hard
drives or partitions). The aim is to allow file systems to be added or
removed from the partition set while the system is running and partitions
may be added to a set (or removed if the remaining partitions have enough
space to contain all the data) while the system is running.The two main aims are to allow a number of mountable
file systems to share the same pool of storage space (IE have the user
home dirs on the same drive as the news spool but have separate accounting
for them), and to allow the easy addition of more hard drives to allow
more space.</P>
<P>Some other features that authors want to implement are
<A HREF="Filesystems-HOWTO-1.html#journal">logging/journaling</A>, support
for as many OSs as possible (although all work will be initially done on
Linux), and quotas in the FS so we don't need to waste ages running a silly
quotacheck program at boot - the logging should avoid quotacheck the same
way it avoids fsck! They want to be able to boot a system with 10gig of news
spread over 4 hard drives with full quotas AFTER a power failure with less
than 20 seconds for mounting file systems!</P>
<P>Homepage of Enhanced FS is at
<A HREF="http://www.coker.com.au/~russell/enh/">http://www.coker.com.au/~russell/enh/</A>.
Contact Russell Coker
&lt;
<A HREF="mailto:russell@coker.com.au">russell@coker.com.au</A>&gt; for more information.</P>
<H2><A NAME="efs"></A> <A NAME="ss9.8">9.8</A> <A HREF="Filesystems-HOWTO.html#toc9.8">EFS - Extent filesystem (IRIX)</A>
</H2>
<P>The Extent File System (efs) is Silicon Graphics' early block-device
filesystem, widely used on pre-6.0 versions of IRIX. Since 6.0, xfs
has been bundled with IRIX and users are being encouraged to migrate
to xfs filesystems. IRIX support for efs will be read-only in versions
of IRIX beyond 6.5, however efs is still very much in use on SGI
software distribution CDs.</P>
<P>There are two kernel modules for linux to access EFS filesystem.</P>
<P>
<A NAME="efs_linux"></A> </P>
<P>
<UL>
<LI> Homepage:
<A HREF="http://aeschi.ch.eu.org/efs/">http://aeschi.ch.eu.org/efs/</A></LI>
<LI> Download:
<A HREF="http://aeschi.ch.eu.org/efs/efs-1.0b.tar.gz">http://aeschi.ch.eu.org/efs/efs-1.0b.tar.gz</A></LI>
<LI> Author: Al Smith &lt;
<A HREF="mailto:Al.Smith@aeschi.ch.eu.org">Al.Smith@aeschi.ch.eu.org</A>&gt;</LI>
<LI> License: GPL</LI>
<LI> Access: Read-only</LI>
</UL>
The efs kernel module is an implementation of
the extent file system for linux 2.2 kernels. An efs implementation
(efsmod-0.6.tar.gz) was originally written for 1.x kernels by
Christian Vogelgsang.
In this implementation the code has undergone a complete rewrite
and is also endian-clean. To use the efs module, you will need
to have at least a 2.2 kernel. To mount IRIX CDs, your CD-ROM
will need to be able to cope with 512-byte blocks.
This version of efs contains support for hard-disk partitions, and also
contains a kernel patch to allow you to install the efs code into your
linux kernel tree. Handling of large files has also been vastly improved.</P>
<P>Original efsmod is also available:</P>
<P>
<A NAME="efsmod_linux"></A> </P>
<P>
<UL>
<LI> Homepage:
<A HREF="http://wwwcip.informatik.uni-erlangen.de/user/cnvogelg/proj.html">http://wwwcip.informatik.uni-erlangen.de/user/cnvogelg/proj.html</A></LI>
<LI> Download:
<A HREF="http://wwwcip.informatik.uni-erlangen.de/user/cnvogelg/bin/efsmod-0.6.tgz">http://wwwcip.informatik.uni-erlangen.de/user/cnvogelg/bin/efsmod-0.6.tgz</A></LI>
<LI> Author: Christian Vogelgsang</LI>
<LI> License: GPL</LI>
<LI> Access: Read-only</LI>
</UL>
Efs-mod 0.6 is original EFS read/only module for Linux. Version 0.6 finished but
Project frozen due to lack of time and information for implementing the write
part.</P>
<H3>Accessing EFS from Windows NT/95</H3>
<P>
<A NAME="efs_win95"></A> </P>
<P>
<UL>
<LI> Download:
<A HREF="ftp://ivo.cps.unizar.es/pub/SPDsoft/winefssh.exe.zip">ftp://ivo.cps.unizar.es/pub/SPDsoft/winefssh.exe.zip</A></LI>
<LI> Author: J.A. Gutierrez &lt;
<A HREF="mailto:spd@ivo.cps.unizar.es">spd@ivo.cps.unizar.es</A>&gt;</LI>
<LI> License: GPL</LI>
<LI> Access: Read/Only IRIX EFS</LI>
</UL>
Simple program for accessing EFS from Windows 95 (compiled using MS VC++).</P>
<H3>EFS and FFS library, libfs</H3>
<P>
<A NAME="libfs"></A> </P>
<P>
<UL>
<LI> Download:
<A HREF="ftp://ivo.cps.unizar.es/pub/SPDsoft/libfs.tar.gz">ftp://ivo.cps.unizar.es/pub/SPDsoft/libfs.tar.gz</A></LI>
<LI> Author: J.A. Gutierrez &lt;
<A HREF="mailto:spd@ivo.cps.unizar.es">spd@ivo.cps.unizar.es</A>&gt;</LI>
<LI> License: GPL</LI>
<LI> Access: Read/Only IRIX EFS and Sun UFS</LI>
</UL>
A C library to read EFS and FFS from WinNT x86, SunOS
and IRIX. Easy to use (Posix like interface) and to links aginst existent
code FTP server has also winefssh.exe and winufssh.exe,
simple WinNT binaries to interactively read UFS and EFS file systems.
Not a very polished/documented package, but somebody may find it useful.</P>
<P>Useful links:
<UL>
<LI> IRIX EFS filesystem brief description:
<A HREF="http://squish.ucs.indiana.edu:80/ebt-bin/nph-dweb/dynaweb/SGI_Admin/IA_DiskFiles/@ebt-link;td=8?target=%25N%14_7484_START_RESTART_N%25">http://squish.ucs.indiana.edu:80/ebt-bin/nph-dweb/dynaweb/SGI_Admin/IA_DiskFiles/@ebt-link;td=8?target=%25N%14_7484_START_RESTART_N%25</A>
</LI>
</UL>
</P>
<H2><A NAME="ffs"></A> <A NAME="ss9.9">9.9</A> <A HREF="Filesystems-HOWTO.html#toc9.9">FFS - BSD Fast filesystem</A>
</H2>
<P>This is native filesystem for most BSD unixes (FreeBSD, NetBSD, OpenBSD,
Sun Solaris, ...).</P>
<P>See also:
<A HREF="#sfs">SFS, secure filesystem</A>,
<A HREF="#ufs">UFS</A>.</P>
<H3>Accessing FFS from MacOS</H3>
<P>You can expand .tar.gz files to FFS filesystem with BSD Installer utility,
with comes with OpenBSD. It lives at
<A HREF="ftp://ftp.openbsd.org/pub/OpenBSD/2.7/mac68k/utils/">ftp://ftp.openbsd.org/pub/OpenBSD/2.7/mac68k/utils/</A>.</P>
<H2><A NAME="ss9.10">9.10</A> <A HREF="Filesystems-HOWTO.html#toc9.10">GPFS - General Parallel Filesystem</A>
</H2>
<P>This is a UNIX(tm) operating system style file
system designed for the RS/6000 SP(tm) server. It allows
applications on multiple nodes to share file data. GPFS
supports very large file systems and stripes data across
multiple disks for higher performance. GPFS is based on a
shared disk model which provides lower overhead access to
disks not directly attached to the application nodes and
uses a distributed locking protocol to provide full data
coherence for access from any node. It offers many of the
standard AIX(tm) file system interfaces allowing most
applications to execute without modification or
recompiling. These capabilities are available while
allowing high speed access to the same data from all
nodes of the SP system, and providing full data coherence
for operations occurring on the various nodes. GPFS
attempts to continue operation across various node and
component failures assuming that sufficient resources
exist to continue.</P>
<P>
<UL>
<LI>
<A HREF="http://www.austin.ibm.com/resource/technology/paper1.html">http://www.austin.ibm.com/resource/technology/paper1.html</A></LI>
</UL>
</P>
<H2><A NAME="ss9.11">9.11</A> <A HREF="Filesystems-HOWTO.html#toc9.11">HFS - HP-UX Hi performance filesystem</A>
</H2>
<P>This is the second hfs that appears in this howto. It is used in older HP-UX
versions.</P>
<H2><A NAME="htfs"></A> <A NAME="ss9.12">9.12</A> <A HREF="Filesystems-HOWTO.html#toc9.12">HTFS - High throughput filesystem </A>
</H2>
<P>Useful links:
<UL>
<LI> SCO OpenServer 5 filesystems whitepaper:
<A HREF="http://www.sco.com/products/Whitepapers/family/filesy4.htm">http://www.sco.com/products/Whitepapers/family/filesy4.htm</A></LI>
</UL>
</P>
<P>Read/Write <B>commercial</B> driver available from CrosStor:</P>
<P>
<A NAME="htfs_solaris"></A> </P>
<P>
<UL>
<LI> Download:
<A HREF="ftp://ftp.crosstor.com/pub/HTFS/">ftp://ftp.crosstor.com/pub/HTFS/</A></LI>
<LI> License: Commercial?</LI>
<LI> Access: Read/Write</LI>
</UL>
</P>
<H2><A NAME="jfs"></A> <A NAME="ss9.13">9.13</A> <A HREF="Filesystems-HOWTO.html#toc9.13">JFS - Journaled filesystem (HP-UX, AIX, OS/2 5, Linux)</A>
</H2>
<P>
<UL>
<LI> Homepage:
<A HREF="http://oss.software.ibm.com/developerworks/opensource/jfs/">http://oss.software.ibm.com/developerworks/opensource/jfs/</A></LI>
<LI> Download:
<A HREF="http://www10.software.ibm.com/developer/opensource/jfs/project/pub/">http://www10.software.ibm.com/developer/opensource/jfs/project/pub/</A></LI>
<LI> Author: Steve Best &lt;
<A HREF="mailto:sbest@us.ibm.com">sbest@us.ibm.com</A>&gt; and
Dave Kleikamp &lt;
<A HREF="mailto:shaggy@us.ibm.com">shaggy@us.ibm.com</A>&gt;</LI>
<LI> License: GPL</LI>
<LI> Access: ?</LI>
</UL>
JFS is IBM's journaled file system technology, currently used in
IBM enterprise servers, and is designed for high-throughput server
environments.</P>
<H2><A NAME="ss9.14">9.14</A> <A HREF="Filesystems-HOWTO.html#toc9.14">LFS - Linux log structured filesystem</A>
</H2>
<P>Linux Log structured filesystem implementation called d(t)fs:
<UL>
<LI> Homepage:
<A HREF="http://www.complang.tuwien.ac.at/czezatke/lfs.html">http://www.complang.tuwien.ac.at/czezatke/lfs.html</A></LI>
<LI> Author: Christian Czezatke &lt;
<A HREF="mailto:e9025461@student.tuwien.ac.at">e9025461@student.tuwien.ac.at</A>&gt;</LI>
<LI> License: GPL</LI>
<LI> Access: rw/long filenames, etc</LI>
</UL>
d(t)fs is a log-structured filesystem project for Linux.
Currently, the filesystem is mostly up and running,
but no cleaner has been written so far. </P>
<P>There will also be a dtfs mailing list that will be announced on the
homepage. For more information you can have a look at:
<A HREF="http://www.xss.co.at/mailman/listinfo.cgi/dtfs">http://www.xss.co.at/mailman/listinfo.cgi/dtfs</A></P>
<P>
<UL>
<LI>
<A HREF="http://collective.cpoint.net/lfs/">http://collective.cpoint.net/lfs/</A> - The kfs Homepage
Cornelius "Kees" Cook has started a Linux Log--Structured Filesystem
project before dtfs came to live.</LI>
<LI>
<A HREF="http://lucien.blight.com/~c-cook/prof/lfs/">http://lucien.blight.com/~c-cook/prof/lfs/</A> - Another (death)
LFS implementation ;-)</LI>
<LI>
<A HREF="http://www.eecs.harvard.edu/~margo/usenix.195/">http://www.eecs.harvard.edu/~margo/usenix.195/</A>
- Margo Seltzer's &lt;
<A HREF="mailto:margo@das.harvard.edu">margo@das.harvard.edu</A>&gt; LFS page</LI>
</UL>
</P>
<H2><A NAME="ss9.15">9.15</A> <A HREF="Filesystems-HOWTO.html#toc9.15">MFS - Macintosh filesystem </A>
</H2>
<P>MFS is original Macintosh filesystem. It has been replaced by HFS / HFS+.
If you can provide further information, mail
<A HREF="mailto:mhi@penguin.cz">me</A> please.</P>
<H2><A NAME="ss9.16">9.16</A> <A HREF="Filesystems-HOWTO.html#toc9.16">Minix filesystem </A>
</H2>
<P>This is Minix native filesystem. It was also used in first versions of Linux.</P>
<H2><A NAME="nwfs"></A> <A NAME="ss9.17">9.17</A> <A HREF="Filesystems-HOWTO.html#toc9.17">NWFS - Novell NetWare filesystem</A>
</H2>
<P>NWFS is native in Novell NetWare OS. It is modified FAT-based filesystem.
Two variants of this filesystem exists. 16bit NWFS 286 is used in NetWare 2.x.
NetWare 3.x, 4.x and 5 use 32bit NWFS 386.</P>
<H3><A NAME="nwfs286"></A> NetWare filesystem / 286</H3>
<P>(todo)</P>
<H3><A NAME="nwfs386"></A> NetWare filesystem / 386</H3>
<P>(todo)</P>
<H3>Accessing NWFS-386 from Linux</H3>
<P>
<UL>
<LI> Homepage:
<A HREF="http://www.timpanogas.com/html/fenris_for_linux.html">http://www.timpanogas.com/html/fenris_for_linux.html</A></LI>
<LI> Download:
<A HREF="ftp://207.109.151.240/nwfs/">ftp://207.109.151.240/nwfs/</A></LI>
<LI> Author: Timpanogas Research Group, Inc. (jmerkey@timpanogas.com)</LI>
<LI> License: GPL</LI>
<LI> Access: Read-Only</LI>
</UL>
This driver allows you to mount NWFS-386 filesystem on Linux.</P>
<H2><A NAME="nss"></A> <A NAME="ss9.18">9.18</A> <A HREF="Filesystems-HOWTO.html#toc9.18">NSS - Novell Storage Services</A>
</H2>
<P>This is a new 64bit
<A HREF="Filesystems-HOWTO-1.html#journal">journaling</A> filesystem using a
<A HREF="Filesystems-HOWTO-1.html#btree">balanced tree</A> algorithms. It is used in Novell
NetWare 5.</P>
<P>
<UL>
<LI>
<A HREF="http://www.novell.com/whitepapers/nw5/nss.html">http://www.novell.com/whitepapers/nw5/nss.html</A> - NSS Whitepaper</LI>
</UL>
</P>
<H2><A NAME="ss9.19">9.19</A> <A HREF="Filesystems-HOWTO.html#toc9.19">ODS - On Disk Structure filesystem</A>
</H2>
<P>This is OpenVMS and VMS native filesystem.</P>
<H2><A NAME="qnx4"></A> <A NAME="qnxfs"></A> <A NAME="ss9.20">9.20</A> <A HREF="Filesystems-HOWTO.html#toc9.20">QNX filesystem </A>
</H2>
<P>This filesystem is used in QNX. Two major filesystem version exists, version
2 is used by QNX 2 and version 4 by QNX 4. QNX 4 doesn't support version 2 and
vice versa.</P>
<P>QNX4 filesystem is now accessible from Linux 2.1.x+. Say "Y"es to 'QNX
filesystem support';</P>
<P>
<UL>
<LI> Download: In the kernel ;)</LI>
<LI> Author: Frank Denis &lt;
<A HREF="mailto:j@4u.net">j@4u.net</A>&gt; (maintainer),
Richard Frowijn</LI>
<LI> License: GPL</LI>
<LI> Access: Read (except for multi-extents files), Write (experimental)</LI>
</UL>
Driver for the QNX 4 filesystem.</P>
<H2><A NAME="reiserfs"></A> <A NAME="ss9.21">9.21</A> <A HREF="Filesystems-HOWTO.html#toc9.21">Reiser filesystem</A>
</H2>
<P>Reiserfs is a file system using a variant on classical balanced tree
algorithms. The results when compared to the ext2fs conventional block
allocation based file system running under the same operating system
and employing the same buffering code suggest that these algorithms
are more effective for large files and small files not near node size
in time performance, become less effective in time performance and
more significantly effective in space performance as one approaches
files close to the node size, and become markedly more effective in
both space and time as file size decreases substantially below node
size (4k), reaching order of magnitude advantages for file sizes of
100bytes. The improvement in small file space and time performance
suggests that we may now revisit a common OS design assumption that
one should aggregate small objects using layers above the file system
layer.</P>
<P>Useful links:
<UL>
<LI> Reiser fs homepage
<A HREF="http://devlinux.org/namesys/">http://devlinux.org/namesys/</A></LI>
</UL>
</P>
<H2><A NAME="ss9.22">9.22</A> <A HREF="Filesystems-HOWTO.html#toc9.22">RFS (CD-ROM Filesystem)</A>
</H2>
<P>Sony's incremental packet-writing filesystem.</P>
<H2><A NAME="ss9.23">9.23</A> <A HREF="Filesystems-HOWTO.html#toc9.23">RomFS - Rom filesystem</A>
</H2>
<P>Author of Linux RomFS implemplementation is
Janos Farkas &lt;
<A HREF="mailto:chexum@shadow.banki.hu">chexum@shadow.banki.hu</A>&gt; For more information see
<B>/usr/src/linux/Documentation/filesystems/romfs.txt</B>
file.</P>
<H2><A NAME="sfs"></A> <A NAME="ss9.24">9.24</A> <A HREF="Filesystems-HOWTO.html#toc9.24">SFS - Secure filesystem</A>
</H2>
<P>The sfs filesystem type is a variation of the FFS filesystem type. The
boot block,superblock, storage blocks, and free blocks for the sfs
filesystem type are, at the administrative level, identical to those for
FFS. The inodes differ from FFS inodes, however. Each odd-numbered
inode is reserved for security information. The information contains
Access Control List information. I'm not sure if SFS has any other
abilities though.</P>
<P>SFS links:
<UL>
<LI>
<A HREF="http://uw7doc.sco.com/FS_admin/_The_sfs_File_System_Type.html">http://uw7doc.sco.com/FS_admin/_The_sfs_File_System_Type.html</A> - UnixWare 7 documentation: SFS Filesystem</LI>
</UL>
</P>
<H2><A NAME="spiralog"></A> <A NAME="ss9.25">9.25</A> <A HREF="Filesystems-HOWTO.html#toc9.25">Spiralog filesystem (OpenVMS)</A>
</H2>
<P>Spiralog is a 64bit high-performance filesystem for the OpenVMS.
The Spiralog
combines
<A HREF="Filesystems-HOWTO-1.html#journal">log-structured</A> technology
with more traditional
<A HREF="Filesystems-HOWTO-1.html#btree">B-tree</A>
technology to provide a general abstraction. The B-tree
mapping mechanism uses write-ahead logging to give stability and
recoverability guarantees. </P>
<P>Spiralog-related links at Digital:</P>
<P>
<UL>
<LI>
<A HREF="http://www.digital.com/info/SP6048/">http://www.digital.com/info/SP6048/</A>
- Spiralog File System for OpenVMS Alpha </LI>
<LI>
<A HREF="http://www.digital.com/DTJM01/DTJM01AH.HTM">http://www.digital.com/DTJM01/DTJM01AH.HTM</A>
- Overview of the Spiralog File System</LI>
<LI>
<A HREF="http://www.digital.com/DTJM02/DTJM02HM.HTM">http://www.digital.com/DTJM02/DTJM02HM.HTM</A>
- Design of the Server for the Spiralog File System</LI>
</UL>
</P>
<H2><A NAME="ss9.26">9.26</A> <A HREF="Filesystems-HOWTO.html#toc9.26">System V and derived filesystems </A>
</H2>
<P>Homepage of System V Linux project is at
<A HREF="http://www.knm.org.pl/prezes/sysv.html">http://www.knm.org.pl/prezes/sysv.html</A>. Maintainer of
this project is &lt;kgb@manjak.knm.pl.org&gt;.</P>
<H3><A NAME="afs"></A> AFS - Acer Fast Filesystem</H3>
<P>The Acer Fast Filesystem is used on SCO Open Server. It is
similar to the System V Release 4 filesystem, but it is using
bitmaps instead of chained free-list of blocks.</P>
<H3><A NAME="eafs"></A> EAFS - Extended Acer Fast Filesystem</H3>
<P>The AFS filesystem can be 'extended' to handle file names
up to 255 characters, but directories entries still have
14-char names. This filesystem type is used on SCO Open
Server.</P>
<H3><A NAME="coherent"></A> Coherent filesystem</H3>
<H3><A NAME="s5"></A> S5 </H3>
<P>This filesystem is used in UnixWare. It's probably SystemV compatible, but
I haven't verified it yet. For more information see
<A HREF="http://uw7doc.sco.com/FS_admin/_The_s5_File_System_Type.html">http://uw7doc.sco.com/FS_admin/_The_s5_File_System_Type.html</A>.</P>
<H3><A NAME="s51k"></A> S51K - SystemV 1K</H3>
<H3>Version 7 filesystem</H3>
<P>This filesystem type is used on Version 7 Unix for PDP-11 machines.</P>
<H3><A NAME="xenix"></A> Xenix filesystem</H3>
<H2><A NAME="ss9.27">9.27</A> <A HREF="Filesystems-HOWTO.html#toc9.27">Text - (Philips' CD-ROM Filesystem)</A>
</H2>
<P>Philips' standard for encoding disc and track data on audio CDs.</P>
<H2><A NAME="ss9.28">9.28</A> <A HREF="Filesystems-HOWTO.html#toc9.28">UDF - Universal Disk Format (DVD-ROM filesystem)</A>
</H2>
<P>There is a Linux UDF filesystem driver:
<A NAME="udf_linux"></A> </P>
<P>
<UL>
<LI> Homepage:
<A HREF="http://trylinux.com/projects/udf/">http://trylinux.com/projects/udf/</A></LI>
<LI> Download:
<A HREF="http://trylinux.com/projects/udf/udf-0.8.0.1.tar.gz">http://trylinux.com/projects/udf/udf-0.8.0.1.tar.gz</A></LI>
<LI> Author: Dave Boynton &lt;
<A HREF="maito:dave@trylinux.com">dave@trylinux.com</A>&gt;</LI>
<LI> Mailing-list: &lt;linux_udf@hootie.lvld.hp.com&gt;</LI>
<LI> License: GPL</LI>
<LI> Access: Read-only</LI>
</UL>
</P>
<H2><A NAME="ufs"></A> <A NAME="ss9.29">9.29</A> <A HREF="Filesystems-HOWTO.html#toc9.29">UFS</A>
</H2>
<P>Note: People often call
<A HREF="#ffs">BSD Fast Filesystem</A> incorrectly
UFS. FFS and UFS are *diferrent* filesystems. All modern Unixes use FFS
filesystem, not UFS! UFS was used in early BSD versions. You can download
source code at
<A HREF="http://minnie.cs.adfa.edu.au/TUHS/">http://minnie.cs.adfa.edu.au/TUHS/</A>.</P>
<P>Useful links:
<UL>
<LI>
<A HREF="http://www.sun.ca/white-papers/ufs-cluster.html">http://www.sun.ca/white-papers/ufs-cluster.html</A>
- Implementation of write-clustering for Sun's UFS</LI>
</UL>
</P>
<P>See also:
<A HREF="#ffs">BSD FFS</A></P>
<H2><A NAME="v7"></A> <A NAME="ss9.30">9.30</A> <A HREF="Filesystems-HOWTO.html#toc9.30">V7 Filesystem</A>
</H2>
<P>The V7 Filesystem was used in Seventh Edition of UNIX Time Sharing system
(about 1980). For more information see 7th Ed. source code, which is
available from the Unix Archive:
<A HREF="http://minnie.cs.adfa.edu.au/TUHS/">http://minnie.cs.adfa.edu.au/TUHS/</A>.</P>
<H2><A NAME="vxfs"></A> <A NAME="ss9.31">9.31</A> <A HREF="Filesystems-HOWTO.html#toc9.31">VxFS - Veritas filesystem (HP-UX, SCO UnixWare, Solaris)</A>
</H2>
<P>This is commercial filesystem developer by Veritas Inc. You can see it in
HP-UX, SCO UnixWare, Solaris and probably other systems. It has very
interesting features:
Extent based allocation, Journaling, access control lists (ACLs),
up to 2 terabyte large file support, online backup (snapshot filesystem),
BSD style quotas and many more.</P>
<P>Three VxFS versions are available with VxFS:</P>
<P><B> Version 1:</B> This is original VxFS, not commonly in use.</P>
<P><B> Version 2:</B> Support for filesets and dynamic inode allocation.</P>
<P><B> Version 4:</B> Latest version, supports large files and quotas.</P>
<P>Note that HP-UX, Solaris and UnixWare versions use slightly different
structures, so you may not be able to read VxFS when you connect it
to different system. </P>
<P>VxFS related links:
<UL>
<LI>
<A HREF="http://www.veritas.com/">http://www.veritas.com/</A> - Veritas Inc
&lt;
<A HREF="mailto:vx-sales@veritas.com">vx-sales@veritas.com</A>&gt;.</LI>
<LI>
<A HREF="http://uw7doc.sco.com/ODM_FSadmin/CONTENTS.html">http://uw7doc.sco.com/ODM_FSadmin/CONTENTS.html</A>
- VxFS ODM FS Admin - UnixWare 7 (documentation, really good).</LI>
<LI>
<A HREF="http://uw7doc.sco.com/FS_manager/fsD.vxfsopt.html">http://uw7doc.sco.com/FS_manager/fsD.vxfsopt.html</A>
- VxFS FS Manager - UnixWare 7 (documentation).</LI>
<LI>
<A HREF="http://manuals.mchp.siemens.de:80/dynaweb/english/ru544e/drlugueb/o25636e1/@Generic__BookView/1641;cd=3">http://manuals.mchp.siemens.de:80/dynaweb/english/ru544e/drlugueb/o25636e1/@Generic__BookView/1641;cd=3</A>
- VxFS - Reliant Unix.</LI>
</UL>
</P>
<P>See also:
<A HREF="Filesystems-HOWTO-2.html#vxvm">VxVM (Veritas volume manager)</A> and
<A HREF="Filesystems-HOWTO-1.html#journal">journaling filesystems</A>.</P>
<H3>VxTools</H3>
<P>
<A NAME="vxtools"></A>
Unix command-line utilities for accessing VxFS versions 2 and 4 are
available under the GNU GPL:
<UL>
<LI> Homepage:
<A HREF="http://www.penguin.cz/~mhi/fs/vxfs/">http://www.penguin.cz/~mhi/fs/vxfs/</A></LI>
<LI> Download:
<A HREF="ftp://ftp.penguin.cz/pub/users/mhi/vxfs/">ftp://ftp.penguin.cz/pub/users/mhi/vxfs/</A></LI>
<LI> Author: Martin Hinner &lt;
<A HREF="mailto:mhi@penguin.cz">mhi@penguin.cz</A>&gt;</LI>
<LI> Mailing-list: &lt;fs-l@penguin.cz&gt;</LI>
<LI> License: GPL</LI>
<LI> Access: Read-only, command-line utilites</LI>
</UL>
Vxtools is a set of command-line utilites which allow you to access your
VxFS filesystem from Linux (and possibly other Unixes). Current version
can read VxFS versions 2 and 4.</P>
<P>I (mhi) plan also VxFS Linux kernel driver.</P>
<P>AFAIK, Rodney Ramdas &lt;
<A HREF="mailto:rodney@quicknet.nl">rodney@quicknet.nl</A>&gt; works on VxFS driver for FreeBSD. I don't
know current status of his project, so if you want more info contact him
directly.</P>
<H2><A NAME="xfs"></A> <A NAME="ss9.32">9.32</A> <A HREF="Filesystems-HOWTO.html#toc9.32">XFS - Extended filesystem (IRIX)</A>
</H2>
<P>XFS(tm) is the next-generation file system for
Silicon Graphics[TM] systems, from desktop workstations to supercomputers.
XFS provides full 64-bit file capabilities that scale easily to handle
extremely large files and file systems that grow to 1 terabyte. The XFS file
system integrates volume management, guaranteed rate I/O, and
<A HREF="Filesystems-HOWTO-1.html#journal">journaling</A>
technology for fast, reliable recovery. File systems can be backed up while
still in use, significantly reducing administrative overhead.</P>
<P>XFS is designed for a very high performance; sustained throughput in excess
of 300MB per second has been demonstrated on CHALLENGE systems.
The XFS file system scales in performance to match the CHALLENGE MP
architecture. Traditional files, directories, and file systems have reduced
performance as they grow in size. With the XFS file system, there is no
performance penalty. For example, XFS directories have been tested with up to
32 million files in a single directory. </P>
<P>XFS is a journalled file system. It logs changes to the inodes,
directories and bitmaps to the disk before the original entries are updated.
Should the system crash before the updates are done they can be recreated
using the log and updated as intended. </P>
<P>XFS uses a space manager to allocate disk space for the file system and
control the inodes. It uses a namespace manager to control allocation of
directory files. These managers use B-tree indexing to store file location
information, significantly decreasing the access time needed to retrieve file
information. </P>
<P>Inodes are created as needed and are not restricted to a particular area on a
disk partition. XFS tries to position the inodes close to the files and
directories they reference. Very small files, such as symbolic links and
some directories, are stored as part of the inode, to increase performance
and save space. Large directories use B-tree indexing within the directory
file to speed up directory searches, additions and deletions.</P>
<P>Useful XFS links:
<UL>
<LI>
<A HREF="http://www.sgi.com/Technology/xfs-whitepaper.html">http://www.sgi.com/Technology/xfs-whitepaper.html</A>
XFS whitepaper</LI>
</UL>
</P>
<P>XFS Linux port covered by the GNU General Public License is available from
SGI Inc.:
<A NAME="xfs_linux"></A> </P>
<P>
<UL>
<LI> Homepage:
<A HREF="http://oss.sgi.com/projects/xfs/">http://oss.sgi.com/projects/xfs/</A></LI>
<LI> Download:
<A HREF="ftp://oss.sgi.com/www/projects/xfs/download/">ftp://oss.sgi.com/www/projects/xfs/download/</A></LI>
<LI> Author: SGI Inc.,
<A HREF="http://www.sgi.com/">http://www.sgi.com/</A></LI>
<LI> License: GPL</LI>
<LI> Access: Read-write</LI>
</UL>
</P>
<H2><A NAME="xia"></A> <A NAME="ss9.33">9.33</A> <A HREF="Filesystems-HOWTO.html#toc9.33">Xia FS</A>
</H2>
<P>This filesystem was developed to replace old Minix filesystem in Linux. Author
of this fs is Franx Xia &lt;
<A HREF="mailto:qx@math.columbia.edu">qx@math.columbia.edu</A>&gt;</P>
<HR>
<A HREF="Filesystems-HOWTO-10.html">Next</A>
<A HREF="Filesystems-HOWTO-8.html">Previous</A>
<A HREF="Filesystems-HOWTO.html#toc9">Contents</A>
</BODY>
</HTML>
Reference in New Issue View Git Blame Copy Permalink