From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Chow Subject: Re: [ANNOUNCE] Lustre Lite 1.0 beta 1 Date: Tue, 18 Mar 2003 01:13:50 +0800 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <3E76024E.9060607@shaolinmicro.com> References: <20030312175625.GL888@peter.cfs> <3E740DE1.6010204@shaolinmicro.com> <20030316013858.C12806@schatzie.adilger.int> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Braam , linux-fsdevel@vger.kernel.org Return-path: To: Andreas Dilger List-Id: linux-fsdevel.vger.kernel.org > > >Well, each OST is primarily (from the Lustre sense) the network interface >protocol, and the internal implementation is opaque to the outside world. >Each OST is independent of the others, although the clients end up allocating >files on all of them. > >For Linux OSTs we use ext3 on regular block devices (raw disk, MD RAID, >LOV, whatever you want to use) for the actual data storage, and the >filesystem is journaled/managed totally independent from all of the >other OSTs. We have also used reiserfs for OST storage at times (and >concievably you could use XFS/JFS), and there are also 3rd party vendors >who are building OST boxes with their own non-Linux internals. > >Since this is just regular disk attached to regular Linux boxes, it is >also possible to do storage server failover (already being implemented) >without clients even being aware of a problem. Single disk failure is >expected to be handled by RAID of some kind. > >Cheers, Andreas > > Andreas, Thanks for your lengthly explanation. The design looked like Coda with OST as you refer to the actual data storage. In fact, it is a stacked file cache or your store data in files persistently on existing file systesms. However, how can it handle a disconnected storage server? Where this is the most diffcult problem for any cluster file systems that support disconnection. It is obviously not allow disconnection for system like having thousands of nodes is bad. The chance of node failure is very high in those cases. As file allocation is still allowed to be done across multiple storage servers. The answer to resolving data conflicts transparently after disconnection is impossible! I would really like to hear this from Lustre as it already played around with 1000 nodes. When I came down to design a distributed file system end up blowing my head about this. Thanks for comments or may yo give some directions for me as I am very interested in this topic. regards, David Chow