Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Allison Henderson <achender@linux.vnet.ibm.com>
Cc: Ted Ts'o <tytso@mit.edu>, Curt Wohlgemuth <curtw@google.com>,
	Yongqiang Yang <xiaoqiangnk@gmail.com>,
	Surbhi Palande <csurbhi@gmail.com>, Rafael Wysocki <rjw@sisk.pl>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Bug with "fix partial page writes" [3.2-rc regression]
Date: Tue, 6 Dec 2011 14:47:02 -0800 (PST)	[thread overview]
Message-ID: <alpine.LSU.2.00.1112061432000.1949@sister.anvils> (raw)
In-Reply-To: <4EDE85F4.4020503@linux.vnet.ibm.com>

On Tue, 6 Dec 2011, Allison Henderson wrote:
> On 12/06/2011 01:55 AM, Hugh Dickins wrote:
> > On Mon, 5 Dec 2011, Allison Henderson wrote:
> > > 
> > > Have you tried Yongqiang's patch "[PATCH 1/2] ext4: let mpage_submit_io
> > > works well when blocksize<  pagesize" ?  I have tried it and it does
> > > seem to
> > > help, but I am still running into some failures that I am trying to
> > > debug,
> > > but let please let us know if it helps the issues that you are seeing.
> > > Thx!
> > 
> > That 1/2, or the 2/2 "ext4: let ext4_discard_partial_buffers handle
> > pages without buffers correctly"?  The latter is mostly a reversion
> > of your 02fac1297eb3, so that's the one I need to fix the oops and
> > rare data corruption.  Perhaps you're suggesting 1/2 for fsx failures
> > under memory pressure?
> > 
> > I've now tried the fsx test on three machines, with both 1/2 and 2/2
> > applied to 3.2-rc4.  On one machine, with ext2 on loop on tmpfs, the
> > fsx test failed in a couple of minutes with those patches; on another
> > machine, with ext2 on loop on tmpfs, it failed after about 40 minutes
> > with  the patches; on this laptop, with ext2 on SSD, it's just now
> > failed after 35 minutes with the patches.
> > 
> > That's not to say that Yongqiang's patches aren't good; but I cannot
> > detect whether they make any improvement or not, since lasting for 2 or
> > 40 minutes is typical for fsx under memory pressure with recent kernels.
> 
> 
> Well, initially I meant to just try the whole set, but now that I try just
> one of them, I find that I get further with only the first one.  I think
> Yongqiang and I have a similar set up because I get the hang if I dont have
> the first patch, and I get the fsx write failure (in about 20 or so minutes)
> if I have the second one.  But I think Yongqiang's right, we need to figure
> out why the page is uptodate when it shouldn't be.

I've not seen a hang myself.  I'm reluctant to drop the second patch,
since it appears to fix the real problems (oops and corruption) that
I have seen, and fsx fails with or without it; but I don't know whether
it's any better than simply reverting yours.

I would certainly like fsx under memory pressure to be reliable again -
that will help all our testing of new changes; but I think it's more
urgent to get normal loads to be reliable again.

If you can call building on -t ext2 -b 1024 under memory pressure normal ;)

Hugh

  reply	other threads:[~2011-12-06 22:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 22:59 Bug with "fix partial page writes" Curt Wohlgemuth
2011-11-20 20:59 ` Hugh Dickins
2011-11-21  1:59   ` Yongqiang Yang
2011-11-21 17:38     ` Allison Henderson
     [not found]       ` <CAMBkX3cfQ+XS7M5jvXmj8_rBOJ_Afy+YXL7Roj+fswLqBA7i1Q@mail.gmail.com>
2011-11-21 21:26         ` Fwd: " Surbhi Palande
2011-11-22 15:57           ` Allison Henderson
2011-11-22  1:44       ` Yongqiang Yang
2011-11-21 16:56   ` Ted Ts'o
2011-11-21 22:04     ` Hugh Dickins
2011-12-05 23:38       ` Bug with "fix partial page writes" [3.2-rc regression] Hugh Dickins
2011-12-06  1:40         ` Allison Henderson
2011-12-06  3:08           ` Yongqiang Yang
2011-12-06  3:20             ` Yongqiang Yang
2011-12-06  3:33             ` Tao Ma
2011-12-06  3:44               ` Yongqiang Yang
2011-12-06  4:05                 ` Allison Henderson
2011-12-06  7:57                   ` Yongqiang Yang
2011-12-06  8:55           ` Hugh Dickins
2011-12-06  9:32             ` Yongqiang Yang
2011-12-06 22:31               ` Hugh Dickins
2011-12-06 21:15             ` Allison Henderson
2011-12-06 22:47               ` Hugh Dickins [this message]
2011-12-07  8:28               ` Yongqiang Yang
2011-12-07 17:04                 ` Allison Henderson
2011-12-08  5:10                   ` Allison Henderson
2011-12-08 17:39                     ` Hugh Dickins
2011-12-08 18:12                       ` Andy Whitcroft
2011-12-09 13:33                         ` Andy Whitcroft
2011-12-09 13:44                           ` Yongqiang Yang
2011-12-09 16:37                             ` Allison Henderson
2011-12-14  4:12                       ` Ted Ts'o
2011-12-14 18:07                         ` Hugh Dickins

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=alpine.LSU.2.00.1112061432000.1949@sister.anvils \
    --to=hughd@google.com \
    --cc=achender@linux.vnet.ibm.com \
    --cc=csurbhi@gmail.com \
    --cc=curtw@google.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=tytso@mit.edu \
    --cc=xiaoqiangnk@gmail.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