From: Mark Fasheh <mfasheh@suse.de>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>,
Qu Wenruo <quwenruo@cn.fujitsu.com>,
Mark Fasheh <mfasheh@suse.de>
Subject: [PATCH 0/2] btrfs-progs: qgroup verification update
Date: Wed, 15 Jun 2016 15:50:00 -0700 [thread overview]
Message-ID: <1466031002-14533-1-git-send-email-mfasheh@suse.de> (raw)
Hi David,
The following two patches update the qgroup verification code in btrfsck to
understand entire qgroup hierarchies. The first patch is a simple bugfix
for some leaked objects and can be taken separately if you like. The 2nd
patch implements the actual verification update.
If you prefer to pull via git there is a branch at:
https://github.com/markfasheh/btrfs-progs-patches qgroup-hierarchy
Review and comments are welcome.
Thanks,
--Mark
next reply other threads:[~2016-06-15 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 22:50 Mark Fasheh [this message]
2016-06-15 22:50 ` [PATCH 1/2] btrfs-progs: free qgroup counts in btrfsck Mark Fasheh
2016-06-17 15:34 ` David Sterba
2016-06-15 22:50 ` [PATCH 2/2] btrfs-progs: btrfsck: verify qgroups above level 0 Mark Fasheh
2016-06-17 15:34 ` 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=1466031002-14533-1-git-send-email-mfasheh@suse.de \
--to=mfasheh@suse.de \
--cc=dsterba@suse.cz \
--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).