[OpenAFS-devel] Re: OpenAFS-devel digest, Vol 1 #814 - 2 msgs

[Nathan Neulinger]

There are two backends currently:

	1. NAMEI - works on just about anything
	2. Inode - direct storage of data in the inodes of the underlying
filesystem - requires kernel support and only works right on some
filesystems and only on certain platforms. Doesn't really take advantage
of the underlying filesystem.

It might be nice for example to make use of reiserfs's underlying
filesystem structures to more efficiently serve data to afs, or directly
make use of other fs specific features, etc. - or implement a NAMEI
based server that operated more efficiently. I believe that sort of this
is what Harald was referring to.

-- Nathan

On Mon, 2003-05-05 at 11:22, Henry B. Hotz wrote:
> At 12:01 PM -0400 5/5/03, openafs-devel-request@openafs.org wrote:
> >Date: Sun, 04 May 2003 22:14:42 +0200 (CEST)
> >To: weisong@cs.wayne.edu, weisong@cs.nyu.edu
> >Cc: openafs-devel@openafs.org
> >Subject: Re: [OpenAFS-devel] how can we contribute the development of
> >  OpenAFS?
> >From: Harald Barth <haba@pdc.kth.se>
> >
> >       File server backend: It would be nice if there would be a
> >       possibility to add different storage backends.
> 
> What, exactly, do you mean by a back end?
> 
> My (incomplete) understanding is that it has to support direct access 
> using inodes.  This would imply that any hardware RAID would work. 
> Some (most?) software RAIDs would also work.  You have to use a 
> filesystem type that supports those features.
-- 

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216