| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Fri, 28 Sep 2001 13:27:52 +0200 |
| Cc: | Sebastian Kun <seb@xxxxxxxxxxxxx>, shyberts@xxxxxxxxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <200109271535.f8RFZf908442@jen.americas.sgi.com>; from lord@sgi.com on Thu, Sep 27, 2001 at 10:35:41AM -0500 |
| References: | <seb@consensys.com> <200109271535.f8RFZf908442@jen.americas.sgi.com> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Thu, Sep 27, 2001 at 10:35:41AM -0500, Steve Lord wrote: > GFS is one filesystem which is capable of this - it is a complete filesystem, > not a layer which sits on top of another filesystem. It does cache coherency > by locking regions of the disk using a semaphore device (can be a software > device). GFS was initially developed on Irix, but I am pretty sure the latest > stuff is linux only - they also just removed it from under the GPL. We, the OpenGFS group (http://www.opengfs.org) are working on OpenGFS which is a free fork of GFS. Currently we are working on OpenGFS 0.1 which is GFS 4.1 minus the truckload of bugs Sistina has in it's code base. After that OpenGFS will diverged more, but trying to stay ondisk and - if possible - protocol compatible to GFS 4.x Christoph -- Of course it doesn't work. We've performed a software upgrade. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | wbee (sample_hsm) dumped core, Takayuki Sasaki |
|---|---|
| Next by Date: | xfsdump/restore from cd, Charles Radeke |
| Previous by Thread: | Re: XFS and OpenAFS (was Re[2]: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ? ), P.Dixon |
| Next by Thread: | Re: XFS (v.1.0.1 for RedHat 7.1) and XFS (Irix 6.5.13m) differ?, Russell Cattelan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |