From owner-freebsd-fs@FreeBSD.ORG Wed Jul 20 12:34:31 2005 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7779116A41F for ; Wed, 20 Jul 2005 12:34:31 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FDD643D46 for ; Wed, 20 Jul 2005 12:34:30 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j6KCYKgk055315; Wed, 20 Jul 2005 07:34:24 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42DE44CA.7080503@centtech.com> Date: Wed, 20 Jul 2005 07:34:18 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: yfyoufeng@263.net References: <200507020038.j620cO7F071025@gate.bitblocks.com> <42DDB3F2.7020000@centtech.com> <1121826946.2235.6.camel@localhost.localdomain> In-Reply-To: <1121826946.2235.6.camel@localhost.localdomain> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: ClamAV 0.82/984/Tue Jul 19 04:16:09 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: Cluster Filesystem for FreeBSD - any interest? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2005 12:34:31 -0000 yf-263 wrote: > =E5=9C=A8 2005-07-19=E4=BA=8C=E7=9A=84 21:16 -0500=EF=BC=8CEric Anderso= n=E5=86=99=E9=81=93=EF=BC=9A >=20 >>Bakul Shah wrote: >>[..snip..] >> >>>>:) I understand. Any nudging in the right direction here would be >>>>appreciated. >>> >>> >>>I'd probably start with modelling a single filesystem and how >>>it maps to a sequence of disk blocks (*without* using any >>>code or worrying about details of formats but capturing the >>>essential elements). I'd describe various operations in >>>terms of preconditions and postconditions. Then, I'd extend >>>the model to deal with redundancy and so on. Then I'd model >>>various failure modes. etc. If you are interested _enough_ >>>we can take this offline and try to work something out. You >>>may even be able to use perl to create an `executable' >>>specification:-) >> >>I've done some research, and read some books/articles/white papers sinc= e=20 >>I started this thread. >> >>First, porting GFS might be a more universal effort, and might be=20 >>'easier'. However, that doesn't get us a clustered filesystem with BSD= =20 >>license (something that sounds good to me). >=20 >=20 > It has been said it would be a seven man-month efforts for a FS expert.= Then we need to get a small group together and get started.. >>Clustering UFS2 would be cool. Here's what I'm looking for: >=20 >=20 > It is exactly how "Lustre" doing its work, though it build itself on > Ext3, and Lustre targets at http://www.lustre.org/docs/SGSRFP.pdf . Yes, I've read about lustre. I like the GFS model much better. Eric --=20 ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------