From: Andreas Dilger <adilger@clusterfs.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Lars Marowsky-Bree <lmb@suse.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Benefits from computing physical IDE disk geometry?
Date: Sun, 13 Apr 2003 17:38:10 -0600 [thread overview]
Message-ID: <20030413173810.Z26054@schatzie.adilger.int> (raw)
In-Reply-To: <200304131817_MC3-1-3444-7E2F@compuserve.com>; from 76306.1226@compuserve.com on Sun, Apr 13, 2003 at 06:13:23PM -0400
On Apr 13, 2003 18:13 -0400, Chuck Ebbert wrote:
> Lars Marowsky-Bree wrote:
> > Object Based Storage (see Lustre).
>
> Thanks, I was trying to remember where I'd seen that.
>
> Is anyone actually making such things for sale?
Yes, there is a 3rd party vendor which has already sold a bunch of
Object Storage Targets (OSTs) to LLNL for the MCR cluster, see:
http://www.top500.org/top5/2002/11/five/
http://www.llnl.gov/linux/mcr/
http://www.bluearc.com/news/press_releases/pr_mcr_121102.shtml
These are not the "OST-on-a-disk" paradigm that we first worked on with
Seagate, but rather large NAS/NFS storage servers that also implement
the Lustre network protocol. We are also working with other vendors to
implement Linux-based OST targets (I'm not sure whether I can reveal names
or not) for even larger clusters.
Maybe if Lustre becomes popular enough, we will see Lustre implemented on
single disks. There is an object-based storage group with the SCSI T10
committee, but so far their protocol is mostly unusable for Lustre.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2003-04-13 23:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 22:13 Chuck Ebbert
2003-04-13 23:38 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 13:28 Chuck Ebbert
2003-04-16 23:06 ` Nick Piggin
2003-04-15 18:33 Chuck Ebbert
2003-04-16 1:16 ` Nick Piggin
2003-04-16 1:59 ` Nick Piggin
2003-04-15 1:19 Chuck Ebbert
2003-04-15 8:28 ` Nick Piggin
2003-04-14 21:27 Chuck Ebbert
2003-04-15 0:03 ` Nick Piggin
2003-04-14 3:44 Chuck Ebbert
2003-04-14 2:29 Chuck Ebbert
2003-04-13 18:03 Chuck Ebbert
2003-04-13 18:24 ` Dr. David Alan Gilbert
2003-04-13 18:32 ` Lars Marowsky-Bree
2003-04-13 18:51 ` Dr. David Alan Gilbert
2003-04-13 22:14 ` Alan Cox
2003-04-14 0:17 ` Andreas Dilger
2003-04-13 22:15 ` Alan Cox
2003-04-14 3:58 ` Nick Piggin
2003-04-12 22:46 Timothy Miller
2003-04-13 9:51 ` John Bradford
2003-04-13 11:50 ` Nick Piggin
2003-04-13 15:25 ` Timothy Miller
2003-04-14 3:52 ` Nick Piggin
2003-04-14 6:44 ` Mark Hahn
2003-04-14 13:28 ` Nick Piggin
2003-04-13 14:29 ` Alan Cox
2003-04-13 16:15 ` John Bradford
2003-04-18 13:01 ` Helge Hafting
2003-04-18 13:25 ` John Bradford
2003-04-14 18:27 ` Wes Felter
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=20030413173810.Z26054@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
/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
all inboxes | Powered by JetHome®