xfs
[Top] [All Lists]

Re: [BUG] 2.6.0-test4-mm1: NFS+XFS=data corruption

To: Andrew Morton <akpm@xxxxxxxx>
Subject: Re: [BUG] 2.6.0-test4-mm1: NFS+XFS=data corruption
From: Steve Lord <lord@xxxxxxx>
Date: 26 Aug 2003 12:57:21 -0500
Cc: suparna@xxxxxxxxxx, barryn@xxxxxxxxx, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, linux-mm@xxxxxxxxx, linux-xfs@xxxxxxxxxxx
In-reply-to: <20030826104458.448d1eea.akpm@osdl.org>
Organization:
References: <20030824171318.4acf1182.akpm@osdl.org> <20030825193717.GC3562@ip68-4-255-84.oc.oc.cox.net> <20030825124543.413187a5.akpm@osdl.org> <1061852050.25892.195.camel@jen.americas.sgi.com> <20030826031412.72785b15.akpm@osdl.org> <20030826110111.GA4750@in.ibm.com> <20030826104458.448d1eea.akpm@osdl.org>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Tue, 2003-08-26 at 12:44, Andrew Morton wrote:
> Suparna Bhattacharya <suparna@xxxxxxxxxx> wrote:
> >
> >  > Binary searching reveals that the offending patch is
> >  > O_SYNC-speedup-nolock-fix.patch
> >  > 
> > 
> >  I'm not sure if this would help here, but there is
> >  one bug which I just spotted which would affect writev from
> >  XFS. I wasn't passing the nr_segs down properly.
> 
> That fixes it, thanks.

Does rpm use readv/writev though? Or does the nfs server? not sure
how this change would affect the original problem report.

Steve

-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@xxxxxxx


<Prev in Thread] Current Thread [Next in Thread>