From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <xfs-bounce@oss.sgi.com>
Received: with ECARTIS (v1.0.0; list xfs); Tue, 18 Jul 2006 15:36:54 -0700 (PDT)
Received: from orca.ele.uri.edu (orca.ele.uri.edu [131.128.51.63])
	by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k6IMacDW012775
	for <linux-xfs@oss.sgi.com>; Tue, 18 Jul 2006 15:36:39 -0700
Subject: Re: stable xfs
From: Ming Zhang <mingz@ele.uri.edu>
Reply-To: mingz@ele.uri.edu
In-Reply-To: <17595.47312.720883.451573@base.ty.sabi.co.UK>
References: <1153150223.4532.24.camel@localhost.localdomain>
	 <17595.47312.720883.451573@base.ty.sabi.co.UK>
Content-Type: text/plain
Date: Tue, 18 Jul 2006 18:36:06 -0400
Message-Id: <1153262166.2669.267.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: xfs-bounce@oss.sgi.com
Errors-To: xfs-bounce@oss.sgi.com
List-Id: xfs
To: Peter Grandi <pg_xfs@xfs.for.sabi.co.UK>
Cc: Linux XFS <linux-xfs@oss.sgi.com>

Thanks for your response.

But could you give me an example on what is an improper use?

Ming

On Mon, 2006-07-17 at 17:20 +0100, Peter Grandi wrote:
> >>> On Mon, 17 Jul 2006 11:30:23 -0400, Ming Zhang
> >>> <mingz@ele.uri.edu> said:
> 
> mingz> Hi All We want to use XFS in all of our production
> mingz> servers but feel a little scary about the corruption
> mingz> problems seen in this list. [ ... ]
> 
> XFS is complex but quite stable code. Most of the reports about
> ''corruption'' are consequences of not being aware of what it
> was designed for, how it works and how it should be used...
> 
>