From: Steve Lord <lord@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: suparna@in.ibm.com, barryn@pobox.com,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, linux-xfs@oss.sgi.com
Subject: Re: [BUG] 2.6.0-test4-mm1: NFS+XFS=data corruption
Date: 26 Aug 2003 12:57:21 -0500 [thread overview]
Message-ID: <1061920640.25889.1404.camel@jen.americas.sgi.com> (raw)
In-Reply-To: <20030826104458.448d1eea.akpm@osdl.org>
On Tue, 2003-08-26 at 12:44, Andrew Morton wrote:
> Suparna Bhattacharya <suparna@in.ibm.com> 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@sgi.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-08-26 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 0:13 2.6.0-test4-mm1 Andrew Morton
2003-08-25 6:16 ` pcnet32 oops patches (was Re: 2.6.0-test4-mm1) Barry K. Nathan
2003-08-25 11:00 ` Domen Puncer
2003-08-25 19:37 ` [BUG] 2.6.0-test4-mm1: NFS+XFS=data corruption Barry K. Nathan
2003-08-25 19:45 ` Andrew Morton
2003-08-25 22:54 ` Steve Lord
2003-08-26 10:14 ` Andrew Morton
2003-08-26 11:01 ` Suparna Bhattacharya
2003-08-26 17:44 ` Andrew Morton
2003-08-26 17:57 ` Steve Lord [this message]
2003-08-26 18:34 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1061920640.25889.1404.camel@jen.americas.sgi.com \
--to=lord@sgi.com \
--cc=akpm@osdl.org \
--cc=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@oss.sgi.com \
--cc=suparna@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox