From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pat LaVarre Subject: Re: srfs - a new file system. Date: 24 Oct 2003 14:24:48 -0600 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1067027088.16779.4.camel@patehci2> References: <20031024143829.GB11277@delft.aura.cs.cmu.edu> <20031024141146.O17778@schatzie.adilger.int> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: tzachar@cs.bgu.ac.il, jaharkes@cs.cmu.edu, bulb@ucw.cz, linux-fsdevel@vger.kernel.org Return-path: Received: from email-out2.iomega.com ([147.178.1.83]:12791 "EHLO email.iomega.com") by vger.kernel.org with ESMTP id S262592AbTJXUZM (ORCPT ); Fri, 24 Oct 2003 16:25:12 -0400 To: adilger@clusterfs.com In-Reply-To: <20031024141146.O17778@schatzie.adilger.int> List-Id: linux-fsdevel.vger.kernel.org > > a one to 10^gazillion chance of this happening, > > So, system stabilizes when there are no files left ;-). Anyone have a measure of how often these events actually do occur? What little I've seen people say of how they design file and RAID systems speaks as if HDD's reliably chose either to read back what you wrote to them or else reported an error. What about when the HDD actually reads back something else? How can we know how commonly that occurs in practice, so that we can know how often we're wrong to believe such things as our locally recorded vector time? Pat LaVarre