public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: John Quigley <jquigley@jquigley.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Eric Sandeen <sandeen@sandeen.net>, XFS Development <xfs@oss.sgi.com>
Subject: Re: Best design docs for XFS
Date: Tue, 11 Aug 2009 12:27:21 -0500	[thread overview]
Message-ID: <4A81A9F9.4030509@jquigley.com> (raw)
In-Reply-To: <20090811025356.GA28108@infradead.org>

Christoph Hellwig wrote:
> On Mon, Aug 10, 2009 at 05:56:23PM -0500, Eric Sandeen wrote:
>> It's pretty good still, the fundamental design is not substantially
>> changed; you're more likely to find missing bits than "wrong" bits I think.
>>
>> http://oss.sgi.com/projects/xfs/training/index.html
>>
>> has more info as well.
> 
> The fundamental design is mostly unchanged.  What you might now want to
> bother reading of the original documents are:
> 
>  dir_design.pdf - the dir code has been completely replaced
>  threads.pdf - this is totally IRIX specific
>  scaffold.pdf - again mostly IRIX specific
>  message.pdf - no idea what this is at all, I never saw traces of this in XFS

Thanks a lot guys, that helps.

> For all others there's quite a bit of IRIXism in there.

Ack.

> Is there anything specific you're looking for?

In my work, I've just begun to use XFS as the interface into a very large, virtual storage system, to great effect.  It's my first direct interaction with the file system, and I've been hugely impressed with its power, speed and versatility.

The only unresolved problem that we're experiencing has to do with file system corruption in a failover scenario, and my immediate need in understanding some of the internals is to wrap my hands around this problem (I may email this list with details if I can sufficiently explain myself).

A more long-term need we have is for clustering support.  I've read lightly about CXFS, though it appears to be inactive, or at least not open source.  Has clustering support been discussed with the members here?  If so, I'd like to take part in those conversations if there's sufficient interest to engage in that way.

Thanks very much again.

John Quigley
jquigley.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-08-11 17:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 21:23 Best design docs for XFS John Quigley
2009-08-10 22:56 ` Eric Sandeen
2009-08-11  2:53   ` Christoph Hellwig
2009-08-11 17:27     ` John Quigley [this message]
2009-08-11 17:47       ` Eric Sandeen

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=4A81A9F9.4030509@jquigley.com \
    --to=jquigley@jquigley.com \
    --cc=hch@infradead.org \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    /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