|| ||Boaz Harrosh <firstname.lastname@example.org>|
|| ||Avishay Traeger <email@example.com>, Jeff Garzik <firstname.lastname@example.org>,
Andrew Morton <email@example.com>,
|| ||[PATCHSET 0/8 version 3] exofs|
|| ||Mon, 09 Feb 2009 15:07:42 +0200|
|| ||James Bottomley <James.Bottomley@HansenPartnership.com>,
|| ||Article, Thread
exofs is a file system that uses an OSD device as it's back store.
OSD is a new T10 command set that views storage devices not as a large/flat
array of sectors but as a container of objects, each having a length, quota,
time attributes and more. Each object is addressed by a 64bit ID, and is
contained in a 64bit ID partition. Each object has associated attributes
attached to it, which are integral part of the object and provide metadata about
the object. The standard defines some common obligatory attributes, but user
attributes can be added as needed.
What's new since last iteration:
Lots and lots of changes the actual diff is big.
- mkexofs is removed from Kernel code
Open-osd has a user-mode library now. It is the exact same API (and source) as
the Kernel library. Commands are issued through (patched) bsg.ko. If anyone
is interested see URLs below, patches will be sent to the open-osd-mailing-list.
- Incorporate changes made to ext2 since exofs was first derived.
Thanks to Andrew Morton, I've referred to the git-log of fs/ext2 and
have incorporated all relevant changes into exofs. Lots of bug fixes
and short comings where fixed this way.
- Made everything LE safe.
All on disk types are now using proper Endian types, and properly converted
back and forth. exofs is an LE filesystem just as ext2.
- Completely got rid of IBM API
Previous version was using IBM API for osd commands and those API where implemented
over open-osd in osd.c. open-osd API is now used directly and osd.c is reduced to
a few exofs internal helpers.
- A sleep forever Bug fix, related to async object creation.
- Cleaned up some usage of types, naming conventions, code organization.
Lots of cleanups, and reorganization.
And the regular information for first comers
Our intention with exofs is to make it exportable by Linux
pNFS server, as reference implementation for pNFS-object-layout
server. A pNFS-objects client implementation is also in the works
(See all about pNFS in Linux at:
exofs was originally developed by Avishay Traeger <firstname.lastname@example.org>
from IBM. A very old version of it is hosted on sourceforge as the osdfs
project. The Original code was based on ext2 of the 2.6.10 Kernel and ran
over the old IBM's osd-initiator Linux driver.
Since then it was picked by us, open-osd, and was both forward ported to
current Kernel, as well as converted to run over open-osd Kernel Library.
I have mechanically divided the code in parts, each introducing a
group of vfs function vectors, all tied at the end into a full filesystem.
Each patch can be compiled but it will only run at the very end.
This was done for the hope of easier reviewing.
Here is the list of patches
[PATCH 1/8] exofs: Kbuild, Headers and osd utils
[PATCH 2/8] exofs: file and file_inode operations
[PATCH 3/8] exofs: symlink_inode and fast_symlink_inode operations
[PATCH 4/8] exofs: address_space_operations
[PATCH 5/8] exofs: dir_inode and directory operations
[PATCH 6/8] exofs: super_operations and file_system_type
[PATCH 7/8] exofs: Documentation
[PATCH 8/8] fs: Add exofs to Kernel build
This patchset is also available on:
git-clone git://git.open-osd.org/linux-open-osd.git linux-next
or on the web at:
(Above tree is based on Linus 2.6.29-rc4)
If anyone wants to actually run this code and test it
then please start reading at:
You will need to checkout the out-of-tree git (below) for the user-mode utilities.
Also the exofs.txt file in patch 7/8 should help
If you want to review the user-mode library and supporting plumbings,
patches will be sent to this mailing-list:
And code is on this git-tree:
or on the web at:
Thank you all for the very useful comments, suggestions, and banging me on the
head about the user-mode API.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/