9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: blstuart@bellsouth.net
To: 9fans@9fans.net
Subject: Re: [9fans] Accessing Mac OS Extended drives
Date: Sun,  9 Mar 2014 22:01:43 -0400	[thread overview]
Message-ID: <4e12279bf7a74df2fef43eeab8e7bfa4@bellsouth.net> (raw)
In-Reply-To: <c8bd5cb898f6c95c675450bbdd023cdb@mikro.quanstro.net>

> θfs(4) 	http://www.9atom.org/magic/man2html/4/%CE%B8fs
> is designed for this.  it serves nfs as well as 9p directly.

I've been meaning to send out an announcement for a while, but this
has been a pretty hectic week with the SIGCSE conference.  Thanks to
Coraid and Brantely Coile, I am releasing an early version of the file
system I've been using for several months now.  It's actually the 7th
in a series named by letters from the Greek alphabet.  Some of it's
general characteristics include:

- Runs in user-space on a CPU server or terminal
- When used with the snap device, supports snapshots that are
compatible with the existing file history utilities
- Taking a snapshot is an O(1) operation
- Serves both 9P and NFSv3, including symbolic links and device nodes
- NFS support has been tested with MacOS, Linux, and FreeBSD
- Serves block storage via AoE
- Serves object storage via an experimental object extension to AoE
- There are rough ports to UNIXish systems via P9P
- With suitable changes to boot/local.c, can be used for a file server
root

Some of the downsides are:

- No lock daemon for NFS
- There's an odd error when unmounting from FreeBSD
- Rather un-parsimonious in its space usage: relatively big block
size, no compression, no de-duping (so far)
- No significant work on performance yet
- Very little in the way of documentation

It's been my primary file server since about October.  So as you might
guess, most of the development has taken place on it.  Naturally,
quite a few bugs have been found and sorted out, but I can't make any
guarantees about stability or prime-time readiness.

The snapshot kernel device is available in contrib/blstuart/snap, and
the file system is in contrib/blstuart/θfs.  It's also included in
9atom, and we're working on getting it included in the installer as an
alternative to kfs and fossil-venti.

If you want to use it outside of 9atom, you'll need a modification to
lib9p that's in P9P and 9atom, but as I recall, not in the Labs'
distribution.  In particular, θfs expects the start and end function
pointers in the Srv structure.

Feel free to use it if you have any interest.  I'll be glad to help
try to sort out any issues you run into.

Thanks,
BLS




  parent reply	other threads:[~2014-03-10  2:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  8:44 Rubén Berenguel
2014-03-07  8:54 ` Sergey Zhilkin
2014-03-07  9:00   ` Gorka Guardiola
2014-03-07  9:47     ` David Swasey
2014-03-07 16:49     ` erik quanstrom
2014-03-08 12:30       ` Rubén Berenguel
2014-03-08 12:35         ` erik quanstrom
2014-03-08 12:59           ` Rubén Berenguel
2014-03-08 13:03             ` erik quanstrom
2014-03-08 14:08               ` Rubén Berenguel
2014-03-08 14:18                 ` erik quanstrom
2014-03-08 15:16     ` Jeff Sickel
2014-03-08 17:53       ` Rubén Berenguel
2014-03-08 17:58         ` erik quanstrom
2014-03-08 18:11           ` Rubén Berenguel
2014-03-09 16:42             ` erik quanstrom
2014-03-08 18:27           ` Steve Simon
2014-03-09  8:39             ` Rubén Berenguel
2014-03-09 17:52               ` Jeff Sickel
2014-03-09 18:05                 ` Rubén Berenguel
2014-03-10  2:01           ` blstuart [this message]
2014-03-10  2:08             ` erik quanstrom
2014-03-10  2:19               ` blstuart

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=4e12279bf7a74df2fef43eeab8e7bfa4@bellsouth.net \
    --to=blstuart@bellsouth.net \
    --cc=9fans@9fans.net \
    /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).