From: Mark Fasheh <mfasheh@suse.de>
To: linux-btrfs@vger.kernel.org
Cc: jbacik@fb.com, clm@fb.com, quwenruo@cn.fujitsu.com, mfasheh@suse.de
Subject: [PATCH 0/3] btrfs: update qgroups in drop snapshot, V2
Date: Thu, 5 Nov 2015 14:37:57 -0800 [thread overview]
Message-ID: <1446763080-20235-1-git-send-email-mfasheh@suse.de> (raw)
Hi,
The following 3 patches fix a regression introduced in Linux
4.2 where btrfs_drop_snapshot() wasn't updating qgroups, resulting in
them going bad.
The original e-mail pointing this out is below:
http://www.spinics.net/lists/linux-btrfs/msg46093.html
The first patch is from Josef and fix bugs in our counting of
roots (which is critical for qgroups to work correctly). It was previously
sent to the list:
http://www.spinics.net/lists/linux-btrfs/msg47035.html
Truth be told, most of the time fixing this was spent figuring out that and
another issue (which has also been fixed). Once I realized I was seeing a
bug and we fixed it correctly, my drop snapshot patch got dramatically
smaller.
I also re-added some of the tracing in qgroup.c that we recently
lost. It is again possible to debug qgroup operations on a live
system, allowing us to find issues like the two above by narrowing
down our operations and manually walking through them via
cat sys/debug/tracing.
The entire patch series can be tested in xfstests test btrfs/104.
Thanks,
--Mark
Changes from V1, thanks to Qu for his comments:
- lock around call to btrfs_qgroup_insert_dirty_extent()
- check whether qgroups are enabled in account_leaf_items()
next reply other threads:[~2015-11-05 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 22:37 Mark Fasheh [this message]
2015-11-05 22:37 ` [PATCH 1/3] Btrfs: use btrfs_get_fs_root in resolve_indirect_ref Mark Fasheh
2015-11-05 22:37 ` [PATCH 2/3] btrfs: Add qgroup tracing Mark Fasheh
2015-11-05 22:38 ` [PATCH 3/3] btrfs: qgroup: account shared subtree during snapshot delete Mark Fasheh
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=1446763080-20235-1-git-send-email-mfasheh@suse.de \
--to=mfasheh@suse.de \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).