From: Dmitrii Tcvetkov <demfloro@demfloro.ru>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3.1 1/7] btrfs: Introduce a function to check if all chunks a OK for degraded rw mount
Date: Mon, 1 May 2017 13:21:38 +0300 [thread overview]
Message-ID: <20170501132138.0bd3e33a@job> (raw)
In-Reply-To: <4b9409a0-290a-02d4-4288-2b66c1ed0cd6@cn.fujitsu.com>
> >> +bool btrfs_check_rw_degradable(struct btrfs_fs_info *fs_info)
> >> +{
> >> + struct btrfs_mapping_tree *map_tree = &fs_info->mapping_tree;
> >> + struct extent_map *em;
> >> + u64 next_start = 0;
> >> + bool ret = true;
> >> +
> >> + read_lock(&map_tree->map_tree.lock);
> >> + em = lookup_extent_mapping(&map_tree->map_tree, 0, (u64)-1);
> >> + read_unlock(&map_tree->map_tree.lock);
> >> + /* No chunk at all? Return false anyway */
> >> + if (!em) {
> >> + ret = false;
> >> + goto out;
> >> + }
> >> + while (em) {
> >> + struct map_lookup *map;
> >> + int missing = 0;
> >> + int max_tolerated;
> >> + int i;
> >> +
> >> + map = (struct map_lookup *) em->bdev;
> >
> >
> > any idea why not map = em->map_lookup; here?
>
>
> My fault, will update the patch.
>
> Thanks,
> Qu
Sorry to bother, but looks like this patchset suddenly got forgotten.
It still applies to 4.11 but I'm afraid it won't after 4.12 merge
window. Any update on it?
next prev parent reply other threads:[~2017-05-01 10:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 1:34 [PATCH v3.1 0/7] Chunk level degradable check Qu Wenruo
2017-03-09 1:34 ` [PATCH v3.1 1/7] btrfs: Introduce a function to check if all chunks a OK for degraded rw mount Qu Wenruo
2017-03-13 7:29 ` Anand Jain
2017-03-13 7:25 ` Qu Wenruo
2017-05-01 10:21 ` Dmitrii Tcvetkov [this message]
2017-05-02 0:20 ` Qu Wenruo
2017-05-02 2:28 ` Anand Jain
2017-03-09 1:34 ` [PATCH v3.1 2/7] btrfs: Do chunk level rw degrade check at mount time Qu Wenruo
2017-03-09 1:34 ` [PATCH v3.1 3/7] btrfs: Do chunk level degradation check for remount Qu Wenruo
2017-03-09 1:34 ` [PATCH v3.1 4/7] btrfs: Introduce extra_rw_degrade_errors parameter for btrfs_check_rw_degradable Qu Wenruo
2017-03-09 1:34 ` [PATCH v3.1 5/7] btrfs: Allow barrier_all_devices to do chunk level device check Qu Wenruo
2017-03-13 8:00 ` Anand Jain
2017-03-09 1:34 ` [PATCH v3.1 6/7] btrfs: Cleanup num_tolerated_disk_barrier_failures Qu Wenruo
2017-03-09 1:34 ` [PATCH v3.1 7/7] btrfs: Enhance missing device kernel message Qu Wenruo
2017-06-26 18:59 ` [PATCH v3.1 0/7] Chunk level degradable check David Sterba
2017-06-27 1:05 ` Qu Wenruo
2017-06-27 1:59 ` Anand Jain
2017-06-27 2:49 ` Qu Wenruo
2017-06-27 11:20 ` Austin S. Hemmelgarn
2017-06-27 12:20 ` 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=20170501132138.0bd3e33a@job \
--to=demfloro@demfloro.ru \
--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).