From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Accounting fixes
Date: Wed, 18 Mar 2015 18:59:39 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.03.18.18.59.39@googlemail.com> (raw)
In-Reply-To: 1426624683-3085-1-git-send-email-jbacik@fb.com
On Tue, 17 Mar 2015 16:37:59 -0400, Josef Bacik wrote:
> I've changed all of these a whole bunch recently, I think I've gotten all the
> issues worked out, please review/test to make sure there's not some other
> fucking corner I've missed. Thanks,
So at least for me these seem to fix the problems that happened since the
"account for large extents" patch. Large fallocate/rm cycles no longer trip
over each other with the block group collector, and balance no longer goes
into la-la land waiting for extent bit changes that never show up.
Thanks!
-h
next prev parent reply other threads:[~2015-03-18 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 20:37 [PATCH 0/4] Accounting fixes Josef Bacik
2015-03-17 20:38 ` [PATCH 1/4] Btrfs: account merges/splits properly Josef Bacik
2015-03-18 11:53 ` Filipe David Manana
2015-03-17 20:38 ` [PATCH 2/4] Btrfs: just free dummy extent buffers Josef Bacik
2015-03-18 13:56 ` David Sterba
2015-03-18 13:57 ` Josef Bacik
2015-03-17 20:38 ` [PATCH 3/4] Btrfs: add sanity test for outstanding_extents accounting Josef Bacik
2015-03-17 20:38 ` [PATCH 4/4] Btrfs: fix outstanding_extents accounting in DIO Josef Bacik
2015-03-18 11:55 ` Filipe David Manana
2015-03-18 18:59 ` Holger Hoffstätte [this message]
2015-03-19 12:47 ` [PATCH 0/4] Accounting fixes David Sterba
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=pan.2015.03.18.18.59.39@googlemail.com \
--to=holger.hoffstaette@googlemail.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 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.