From: "Darrick J. Wong" <djwong@us.ibm.com>
To: Theodore Tso <tytso@mit.edu>, "Darrick J. Wong" <djwong@us.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: [RFC 0/2] e2fsprogs: Add FUSE server
Date: Sat, 07 Jan 2012 00:55:23 -0800 [thread overview]
Message-ID: <20120107085523.4325.42183.stgit@elm3c44.beaverton.ibm.com> (raw)
Hi all,
This patchset creates a FUSE server for the ext4 filesystem. This enables ext4
to be run (albeit slowly) in environments which lack a native ext4 driver, such
as Solaris, BSD, and Mac OS X. It uses the functionality in libext2fs to
manipulate the filesystem.
Currently, the filesystem can be mounted for both reading and writing. I
wouldn't mount a production filesystem rw, though in my nail-biting tests so
far it hasn't destroyed anything. Journalling is not supported, though I'm
working on at least enabling journal replay on mount. I suspect that full
journalling (such as what you get with kernel ext4 on Linux) is a long way off.
The performance of fuse2fs (as opposed to kernel ext4) is noticeably slow.
This patchset has been tested on 3.1 on x64 and i386, and Mac OS X. On Linux
you'll need a libfuse that supports the v28 API; on Mac you'll need osxfuse
2.3.8. The patchset is based atop the 1.42 release and requires three patches:
1. libext2fs: Read and write full size inodes
2. libext2fs: When truncating file, punch out blocks at end
3. libext2fs: Only link an inode into a directory once
The first patch is in the metadata checksumming set, and the other two are
general bugfixes that I posted earlier.
Let me know what you think!
--D
next reply other threads:[~2012-01-07 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 8:55 Darrick J. Wong [this message]
2012-01-07 8:55 ` [PATCH 1/2] libext2fs: Add ext2fs_file_get_inode_num call (for fuse2fs) Darrick J. Wong
2012-02-17 15:01 ` Ted Ts'o
2012-01-07 8:55 ` [PATCH 2/2] misc: Add fuse2fs, a FUSE server for e2fsprogs Darrick J. Wong
2012-02-17 15:18 ` Ted Ts'o
2012-02-17 18:51 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120107085523.4325.42183.stgit@elm3c44.beaverton.ibm.com \
--to=djwong@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).