From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Steve Lord <lord@sgi.com>,
barryn@pobox.com, 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: Tue, 26 Aug 2003 16:31:11 +0530 [thread overview]
Message-ID: <20030826110111.GA4750@in.ibm.com> (raw)
In-Reply-To: <20030826031412.72785b15.akpm@osdl.org>
On Tue, Aug 26, 2003 at 03:14:12AM -0700, Andrew Morton wrote:
> Steve Lord <lord@sgi.com> wrote:
> >
> > > > Is this enough information to help find the cause of the bug? If not,
> > > > it might be several days (if I'm unlucky, maybe even a week or two)
> > > > before I have time to do anything more...
> > > >
> > >
> > > -mm kernels have O_DIRECT-for-NFS patches in them. And some versions of
> > > RPM use O_DIRECT. Whether O_DIRECT makes any difference at the server end
> > > I do not know, but it would be useful if you could repeat the test on stock
> > > 2.6.0-test4.
> > >
> > > Alternatively, run
> > >
> > > export LD_ASSUME_KERNEL=2.2.5
> > >
> > > before running RPM. I think that should tell RPM to not try O_DIRECT.
> >
> > I doubt the NFS client is O_DIRECT capable here, I have run some rpm
> > builds over nfs to 2.6.0-test4 and an xfs filesystem, everything is
> > behaving so far. I will try mm1 tomorrow.
> >
> > Do we know if this NFS V3 or V2 by the way?
>
> OK, sorry for the noise. It appears that this is due to the AIO patches in
> -mm. fsx-linux fails instantly on nfsv3 to localhost on XFS. It's OK on
> ext2 for some reason.
>
> 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.
Regards
Suparna
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Labs, India
--- linux-2.6.0-test4-mm1/mm/filemap.c 2003-08-26 10:09:50.000000000 +0530
+++ fix-mm/mm/filemap.c 2003-08-26 16:23:55.000000000 +0530
@@ -1942,7 +1942,7 @@ generic_file_aio_write_nolock(struct kio
goto osync;
}
- ret = __generic_file_aio_write_nolock(iocb, iov, 1, ppos);
+ ret = __generic_file_aio_write_nolock(iocb, iov, nr_segs, ppos);
/*
* Avoid doing a sync in parts for aio - its more efficient to
WARNING: multiple messages have this Message-ID (diff)
From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Steve Lord <lord@sgi.com>,
barryn@pobox.com, 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: Tue, 26 Aug 2003 16:31:11 +0530 [thread overview]
Message-ID: <20030826110111.GA4750@in.ibm.com> (raw)
In-Reply-To: <20030826031412.72785b15.akpm@osdl.org>
On Tue, Aug 26, 2003 at 03:14:12AM -0700, Andrew Morton wrote:
> Steve Lord <lord@sgi.com> wrote:
> >
> > > > Is this enough information to help find the cause of the bug? If not,
> > > > it might be several days (if I'm unlucky, maybe even a week or two)
> > > > before I have time to do anything more...
> > > >
> > >
> > > -mm kernels have O_DIRECT-for-NFS patches in them. And some versions of
> > > RPM use O_DIRECT. Whether O_DIRECT makes any difference at the server end
> > > I do not know, but it would be useful if you could repeat the test on stock
> > > 2.6.0-test4.
> > >
> > > Alternatively, run
> > >
> > > export LD_ASSUME_KERNEL=2.2.5
> > >
> > > before running RPM. I think that should tell RPM to not try O_DIRECT.
> >
> > I doubt the NFS client is O_DIRECT capable here, I have run some rpm
> > builds over nfs to 2.6.0-test4 and an xfs filesystem, everything is
> > behaving so far. I will try mm1 tomorrow.
> >
> > Do we know if this NFS V3 or V2 by the way?
>
> OK, sorry for the noise. It appears that this is due to the AIO patches in
> -mm. fsx-linux fails instantly on nfsv3 to localhost on XFS. It's OK on
> ext2 for some reason.
>
> 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.
Regards
Suparna
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Labs, India
--- linux-2.6.0-test4-mm1/mm/filemap.c 2003-08-26 10:09:50.000000000 +0530
+++ fix-mm/mm/filemap.c 2003-08-26 16:23:55.000000000 +0530
@@ -1942,7 +1942,7 @@ generic_file_aio_write_nolock(struct kio
goto osync;
}
- ret = __generic_file_aio_write_nolock(iocb, iov, 1, ppos);
+ ret = __generic_file_aio_write_nolock(iocb, iov, nr_segs, ppos);
/*
* Avoid doing a sync in parts for aio - its more efficient to
--
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 10:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 0:13 2.6.0-test4-mm1 Andrew Morton
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 6:16 ` Barry K. Nathan
2003-08-25 11:00 ` Domen Puncer
2003-08-25 11:00 ` Domen Puncer
2003-08-25 17:30 ` 2.6.0-test4-mm1: wl3501_cs.c doesn't compile Adrian Bunk
2003-08-25 17:46 ` Arnaldo Carvalho de Melo
2003-08-25 18:24 ` Arnaldo Carvalho de Melo
2003-08-25 18:39 ` Arnaldo Carvalho de Melo
2003-08-25 22:01 ` Adrian Bunk
2003-08-26 15:22 ` Arnaldo Carvalho de Melo
2003-08-25 19:37 ` [BUG] 2.6.0-test4-mm1: NFS+XFS=data corruption Barry K. Nathan
2003-08-25 19:37 ` Barry K. Nathan
2003-08-25 19:45 ` Andrew Morton
2003-08-25 19:45 ` Andrew Morton
2003-08-25 22:54 ` Steve Lord
2003-08-25 22:54 ` Steve Lord
2003-08-26 10:14 ` Andrew Morton
2003-08-26 10:14 ` Andrew Morton
2003-08-26 11:01 ` Suparna Bhattacharya [this message]
2003-08-26 11:01 ` Suparna Bhattacharya
2003-08-26 17:44 ` Andrew Morton
2003-08-26 17:44 ` Andrew Morton
2003-08-26 17:57 ` Steve Lord
2003-08-26 17:57 ` Steve Lord
2003-08-26 18:34 ` Andrew Morton
2003-08-26 18:34 ` Andrew Morton
2003-08-25 23:10 ` 2.6.0-test4-mm1 Martin J. Bligh
2003-08-26 10:08 ` 2.6.0-test4-mm1 William Lee Irwin III
2003-08-26 14:23 ` 2.6.0-test4-mm1 Martin J. Bligh
2003-08-26 14:32 ` 2.6.0-test4-mm1 William Lee Irwin III
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=20030826110111.GA4750@in.ibm.com \
--to=suparna@in.ibm.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=lord@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.