Date: Thu, 23 Oct 2003 08:01:50 -0700 From: Hiten Pandya <hmp@FreeBSD.ORG> To: Terry Lambert <tlambert2@mindspring.com> Cc: freebsd-fs@freebsd.org Subject: Re: >1 systems 1 FS Message-ID: <20031023150150.GA46202@perrin.nxad.com> In-Reply-To: <3F96431E.A30656E3@mindspring.com> References: <3F95B946.8010309@newshosting.com> <20031021233414.GJ99943@elvis.mu.org> <3F95C6F3.8030005@siscom.net> <3F96431E.A30656E3@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 22, 2003 at 01:43:10AM -0700, Terry Lambert wrote: : : [ ... ] : : One example of an FS that can do this is GFS, from Sistina; they : used to have an open-source version (under the GPL), but appear : to have since come to their senses. I ported all the user space : tools for GFS to FreeBSD in about 4 hours of work one night, when : it was still available under the GPL. See their propaganda at: : : http://www.sistina.com/products_gfs.htm On the other hand, you could also check out the OpenGFS project which is still being worked on actively: http://opengfs.sourceforge.net/ This is for Linux, ofcourse. : Anyway, the normal way this is handled for SAN/NAS devices is : to carve out a logical volume region on a per-machine basis, and : forget the locking altogether (giving a management node "ownership" : of the "as yet unallocated regions"), which avoid contention by : separation of the contention domain entirely. Not a very : satisfying way of doing it, if you ask me. You could also checkout another interesting file system, called Lustre, located at http://www.lustre.org/, which could probably help your need. Regards, -- Hiten Pandya hmp@FreeBSD.ORG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031023150150.GA46202>