All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Allison Henderson <achender@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 5/5 v6] ext4: fix partial page writes
Date: Fri, 26 Aug 2011 11:47:13 -0400	[thread overview]
Message-ID: <20110826154713.GB5176@thunk.org> (raw)
In-Reply-To: <1314212842-16741-6-git-send-email-achender@linux.vnet.ibm.com>

On Wed, Aug 24, 2011 at 12:07:22PM -0700, Allison Henderson wrote:
> While running extended fsx tests to verify the preceeding patches,
> a similar bug was also found in the write operation
> 
> When ever a write operation begins or ends in a hole,
> or extends EOF, the partial page contained in the hole
> or beyond EOF needs to be zeroed out.
> 
> To correct this the new ext4_discard_partial_page_buffers_no_lock
> routine is used to zero out the partial page, but only for buffer
> heads that are already unmapped.
> 
> Signed-off-by: Allison Henderson <achender@linux.vnet.ibm.com>

I haven't had a chance to debug this yet, but FYI, with this patch
applied, xfstests #224 causes OOM's to result when running under KVM
with 1024megs.  I tried doubling the memory to 2048 megs, and it
passed in 4k standard ext4 mode, but then got hit with the OOM killer
on test #224 in ext3 emulation mode (nodealloc, and with extents not
enabled in the file system).  Without this patch, and the first four
patches in the v6 patch series applied, xfstests #224 passes in all of
the standard configurations (4k, ext3, 1k, data=journal, etc.)

I don't know why this is happening, but I'll try to dig into it in the
next day or two.  Any thoughts or fixes you might suggest would be
much appreciated.

						- Ted

  reply	other threads:[~2011-08-26 15:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 19:07 [PATCH 0/5 v6] ext4: fix 1k block bugs Allison Henderson
2011-08-24 19:07 ` [PATCH 1/5 v6] ext4: Add new ext4_discard_partial_page_buffers routines Allison Henderson
2011-08-27  4:06   ` Ted Ts'o
2011-08-28  2:22     ` Allison Henderson
2011-08-24 19:07 ` [PATCH 2/5 v6] ext4: fix xfstests 75, 112, 127 punch hole failure Allison Henderson
2011-08-24 19:07 ` [PATCH 3/5 v6] ext4: fix 2nd xfstests " Allison Henderson
2011-08-24 19:07 ` [PATCH 4/5 v6] ext4: fix fsx truncate failure Allison Henderson
2011-08-24 19:07 ` [PATCH 5/5 v6] ext4: fix partial page writes Allison Henderson
2011-08-26 15:47   ` Ted Ts'o [this message]
2011-08-26 22:46     ` Allison Henderson

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=20110826154713.GB5176@thunk.org \
    --to=tytso@mit.edu \
    --cc=achender@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    /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.