From: Steven Cole <elenstev@mesatop.com>
To: Andreas Dilger <adilger@clusterfs.com>, Hans Reiser <reiser@namesys.com>
Cc: darren <teodarren@myrealbox.com>, reiserfs-list@namesys.com
Subject: Re: Object Oriented FS
Date: Mon, 27 Oct 2003 18:40:53 -0700 [thread overview]
Message-ID: <200310271840.53732.elenstev@mesatop.com> (raw)
In-Reply-To: <20031027115622.A17778@schatzie.adilger.int>
On Monday 27 October 2003 11:56 am, Andreas Dilger wrote:
> On Oct 27, 2003 21:23 +0300, Hans Reiser wrote:
> > darren wrote:
> > > allows very high throughput by scaling
> >
> > Do you know what that means? (Seriously, I don't....)
>
> Panasas (from what little I have seen of it) looks to be very similar to
> Lustre. Clients do not access disks directly, but rather have a mapping
> layer between offsets and actual data on disk (similar to LVM and VM
> abstractions of block devices/memory). Once client has this mapping (very
> small in lustre, on the order of a few hundred bytes at most), it
> can do IO directly to one or more storage devices hence scaling of
> throughput proportional to number of storage targets.
>
> In Lustre at least, the client knows nothing about the physical layout of
> blocks in the file on disk, but rather just accesses one or more objects
> via object identifyer, offset, length so the actual layout of the on disk
> data can change.
>
> Lustre is GPL, don't know about Panasas.
>
> Cheers, Andreas
Reading the following, it appears that something _should_ be GPL...
From http://www.panasas.com/object_storage_arch.html
"Panasas is committed to drive the development of standards for the
object-based storage. Through the ANSI T10 committee, Panasas is working with
industry leaders including EMC, IBM, Intel, and Seagate to ensure that
open-source, reference implementations of object-based storage designs are
available and driven through an open standards process."
From http://www.panasas.com/directflow.html
"For the operating system on client server nodes to directly read and write
data objects, an installable file system must be deployed. The DirectFLOW
client installs as a local file system under Linux and is transparent to the
operating system and applications above it. This installable file system
manages the striping of data objects across StorageBlades on a per-object
basis, and unlike standard RAID arrays, has the ability to optimize data
layout and RAID level by each object. DirectFLOW thereby enables
high-performance simultaneous data access for large numbers of clients to
many files."
The fairly large .pdf files available for download seem to be short (2-page),
prettied-up versions of the information available at the above URLs.
Steven
next prev parent reply other threads:[~2003-10-28 1:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 3:46 ReiserFS v3 + millions of files? Dan Oglesby
2003-10-27 6:55 ` Hans Reiser
2003-10-27 9:38 ` Hans Reiser
2003-10-27 11:42 ` Nikita Danilov
2003-10-27 16:03 ` Object Oriented FS darren
2003-10-27 18:23 ` Hans Reiser
2003-10-27 18:43 ` Mike Young
2003-10-27 19:01 ` Hans Reiser
2003-10-27 18:56 ` Andreas Dilger
2003-10-28 1:40 ` Steven Cole [this message]
2003-10-28 4:46 ` lrc1
2003-10-29 6:03 ` ReiserFS v3 + millions of files? Todd Lyons
2003-10-29 8:44 ` Hans Reiser
2003-10-30 6:04 ` Todd Lyons
2003-10-30 7:33 ` Andreas Dilger
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=200310271840.53732.elenstev@mesatop.com \
--to=elenstev@mesatop.com \
--cc=adilger@clusterfs.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=teodarren@myrealbox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.