From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Jan Kara <jack@suse.cz>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: block allocator issue with ext4+DAX
Date: Thu, 31 Mar 2016 09:13:58 -0600 [thread overview]
Message-ID: <20160331151358.GA24866@linux.intel.com> (raw)
In-Reply-To: <20160331085925.GC11041@quack.suse.cz>
On Thu, Mar 31, 2016 at 10:59:25AM +0200, Jan Kara wrote:
> On Wed 30-03-16 16:01:29, Ross Zwisler wrote:
> > I've hit an issue in my testing which I believe to be related to the ext4
> > block allocator when using the DAX mount option. I originally found this
> > issue with the generic/102 xfstest, but have reduced it to the minimal
> > reproducer at the bottom of this email. I've been able to reproduce this with
> > both BRD and with PMEM as the underlying block device.
> >
> > For this test we're running in a very small filesystem, only 512 MiB. We
> > fallocate() 400 MiB of that space, unlink the file, then try and rewrite that
> > 400 MiB file one chunk at a time.
> >
> > What actually happens is that during the rewrite we run out of memory and the
> > DAX call to get_block() in dax_io() fails with -ENOSPC.
>
> Yes, I have already sent a fix for this bug here:
>
> http://www.spinics.net/lists/linux-ext4/msg51649.html
>
> Ted, can you please pick it up? Thanks!
>
> Honza
Yay!
Ted, you can add my
Tested-by: Ross Zwisler <ross.zwisler@linux.intel.com>
to that patch.
Thanks for the fix, Jan!
prev parent reply other threads:[~2016-03-31 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 22:01 block allocator issue with ext4+DAX Ross Zwisler
2016-03-31 8:59 ` Jan Kara
2016-03-31 15:13 ` Ross Zwisler [this message]
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=20160331151358.GA24866@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.