From: ethanwu <ethanwu@synology.com>
To: linux-btrfs@vger.kernel.org
Cc: ethanwu <ethanwu@synology.com>
Subject: [PATCH 0/2] btrfs-progs: check: Handle drop_progress correctly for deleted subvolume
Date: Thu, 13 Oct 2016 19:09:47 +0800 [thread overview]
Message-ID: <1476356989-23131-1-git-send-email-ethanwu@synology.com> (raw)
The patchsets fixes 2 problems in checking deleted subvolume.
First, there are cases missing in checking drop_key, this add up the missing cases,
so the skipping flow could work correctly.
Second, the drop key is only applied to subvolume tree. This should be applied to the
corresponding relocation tree of the deleted subvolume as well.
ethanwu (2):
btrfs-progs: check: skip keys prior to drop key in deleted subvolume
correctly
btrfs-progs: check: add drop key to relocation tree
cmds-check.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
1 file changed, 62 insertions(+), 4 deletions(-)
--
1.9.1
next reply other threads:[~2016-10-13 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 11:09 ethanwu [this message]
2016-10-13 11:09 ` [PATCH 1/2] btrfs-progs: check: skip keys prior to drop key in deleted subvolume correctly ethanwu
2016-10-13 11:09 ` [PATCH 2/2] btrfs-progs: check: add drop key to relocation tree ethanwu
2016-11-15 16:00 ` [PATCH 0/2] btrfs-progs: check: Handle drop_progress correctly for deleted subvolume 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=1476356989-23131-1-git-send-email-ethanwu@synology.com \
--to=ethanwu@synology.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.