Subject: Re: XFS over NFS corruption
From: Craig Tierney <ctierney@hpti.com>
To: Marat Mukhitov <marat@GSTJ2W.stavanger.eur.slb.com>
Cc: Andy <genanr@emsphone.com>, linux-kernel@vger.kernel.org,
       linux-xfs@oss.sgi.com
In-Reply-To: <200406091949.47774.marat@GSTJ2W>
References: <20040609165442.GA9569@thumper2>
	 <200406091949.47774.marat@GSTJ2W>
Content-Type: text/plain
Message-Id: <1086805203.3283.0.camel@hpti9.fsl.noaa.gov>
Mime-Version: 1.0
Date: Wed, 09 Jun 2004 12:20:04 -0600
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1792
Lines: 51

On Wed, 2004-06-09 at 11:49, Marat Mukhitov wrote:
> Andy ,
> 
> We had a similar problem. 
> Changing "async" to "sync" option of exportfs  on NFS server  helps in our case.
> 
> Regards,
> Marat 

Changing that option kills performance though.  Also, in my
case where I am getting corruption, switching to sync did
not help.

Craig

> 
> 
> On Wednesday 09 June 2004 18:54, Andy wrote:
> > I thought I had seen the bug even writing to an non-XFS nfs server, but I
> > can't absolutely confirm this at the time (I was not doing the testing at
> > the time, and some of the result may not have been accurate)
> >
> > But, the description of bug #198 on the XFS bugzilla, does sound like what
> > I am seeing.
> >
> > What I do in my tests is take a file of offsets (every group of 4 bytes
> > contains the offset of the 1st byte of the group) and copy that file to an
> > nfs mounted volume and then compare the local copy to the remote copy
> > (copying to several systems, each server is also receiving from several
> > systems).  After a while I will see errors in the compare, data appearing
> > at the wrong offset in the file.  The amount of data is small (<64k),
> > always an 8k boundary at a large offset discrepancy (100's of megs).  I've
> > attached the mkoffsetfile.c and cmpoffsets.c programs used for testing.
> >
> > Sample of cmpoffsets output :
> >
> > 431128576-431161343 (32768) (held data from 738426880-738459647)
> >  starts at a 65536-byte block
> >  ends at a 524288-byte block
> >
> > Hope this helps.
> >
> > Andy
> 
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/