From: Josef Bacik <josef@redhat.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] Fix ENOSPC regression
Date: Tue, 7 Jun 2011 16:44:07 -0400 [thread overview]
Message-ID: <1307479449-14765-1-git-send-email-josef@redhat.com> (raw)
Sergei accidently introduced a regression with
c4f675cd40d955d539180506c09515c90169b15b
The problem isn't his patch, it's that we are entirely too touchy to changes in
this area because the way we deal with pressure is racy in general. The other
problem is even though delalloc bytes are 0, we still may not have reclaimed
space, rather we need to wait for the ordered extents to reclaim the space. So
this patch set does that and it serialize the flushers to close this race we've
always had. This fixes normal enospc cases we were seeing. Thanks,
Josef
next reply other threads:[~2011-06-07 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 20:44 Josef Bacik [this message]
2011-06-07 20:44 ` [PATCH 1/2] Btrfs: do transaction space reservation before joining the transaction Josef Bacik
2011-06-07 20:44 ` [PATCH 2/2] Btrfs: serialize flushers in reserve_metadata_bytes Josef Bacik
2011-06-09 9:45 ` David Sterba
2011-06-09 14:00 ` Josef Bacik
2011-06-09 18:00 ` David Sterba
2011-06-10 17:47 ` David Sterba
2011-06-10 17:49 ` Josef Bacik
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=1307479449-14765-1-git-send-email-josef@redhat.com \
--to=josef@redhat.com \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).