From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org, dsterba@suse.cz
Cc: ahferroin7@gmail.com, kilobyte@angband.pl, demfloro@demfloro.ru,
Anand Jain <anand.jain@oracle.com>
Subject: Re: [PATCH v4 1/6] btrfs: Introduce a function to check if all chunks a OK for degraded rw mount
Date: Fri, 14 Jul 2017 10:44:20 +0300 [thread overview]
Message-ID: <aebaca38-e283-17bf-c488-bb0d3ac96876@suse.com> (raw)
In-Reply-To: <20170628054335.18806-2-quwenruo@cn.fujitsu.com>
On 28.06.2017 08:43, Qu Wenruo wrote:
> Introduce a new function, btrfs_check_rw_degradable(), to check if all
> chunks in btrfs is OK for degraded rw mount.
>
> It provides the new basis for accurate btrfs mount/remount and even
> runtime degraded mount check other than old one-size-fit-all method.
>
> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> fs/btrfs/volumes.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> fs/btrfs/volumes.h | 1 +
> 2 files changed, 59 insertions(+)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index c95f018d4a1e..7a72fbdb8262 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -6817,6 +6817,64 @@ int btrfs_read_sys_array(struct btrfs_fs_info *fs_info)
> return -EIO;
> }
>
> +/*
> + * Check if all chunks in the fs is OK for read-write degraded mount
> + *
> + * Return true if all chunks meet the minimal RW mount requirement.
> + * Return false if any chunk doesn't meet the minimal RW mount requirement.
> + */
> +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 = em->map_lookup;
> + max_tolerated =
> + btrfs_get_num_tolerated_disk_barrier_failures(
> + map->type);
> + for (i = 0; i < map->num_stripes; i++) {
> + struct btrfs_device *dev = map->stripes[i].dev;
> +
> + if (!dev || !dev->bdev || dev->missing ||
> + dev->last_flush_error)
> + missing++;
> + }
> + if (missing > max_tolerated) {
> + ret = false;
> + btrfs_warn(fs_info,
> + "chunk %llu missing %d devices, max tolerance is %d for writeble mount",
> + em->start, missing, max_tolerated);
> + free_extent_map(em);
> + goto out;
> + }
> + next_start = extent_map_end(em);
> + free_extent_map(em);
> +
> + read_lock(&map_tree->map_tree.lock);
> + em = lookup_extent_mapping(&map_tree->map_tree, next_start,
> + (u64)(-1) - next_start);
> + read_unlock(&map_tree->map_tree.lock);
> + }
> +out:
> + return ret;
> +}
> +
Nit but I think in this function it would be best to directly return
true/false based on context rather than having the superfluous goto.
> int btrfs_read_chunk_tree(struct btrfs_fs_info *fs_info)
> {
> struct btrfs_root *root = fs_info->chunk_root;
> diff --git a/fs/btrfs/volumes.h b/fs/btrfs/volumes.h
> index 6f45fd60d15a..a5897c7a7e86 100644
> --- a/fs/btrfs/volumes.h
> +++ b/fs/btrfs/volumes.h
> @@ -543,4 +543,5 @@ struct list_head *btrfs_get_fs_uuids(void);
> void btrfs_set_fs_info_ptr(struct btrfs_fs_info *fs_info);
> void btrfs_reset_fs_info_ptr(struct btrfs_fs_info *fs_info);
>
> +bool btrfs_check_rw_degradable(struct btrfs_fs_info *fs_info);
> #endif
>
next prev parent reply other threads:[~2017-07-14 7:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 5:43 [PATCH v4 0/6] Chunk level degradable check Qu Wenruo
2017-06-28 5:43 ` [PATCH v4 1/6] btrfs: Introduce a function to check if all chunks a OK for degraded rw mount Qu Wenruo
2017-07-14 7:44 ` Nikolay Borisov [this message]
2017-07-14 8:19 ` Qu Wenruo
2017-07-18 16:29 ` David Sterba
2017-06-28 5:43 ` [PATCH v4 2/6] btrfs: Do chunk level rw degrade check at mount time Qu Wenruo
2017-06-28 5:43 ` [PATCH v4 3/6] btrfs: Do chunk level degradation check for remount Qu Wenruo
2017-06-28 5:43 ` [PATCH v4 4/6] btrfs: Allow barrier_all_devices to do chunk level device check Qu Wenruo
2017-06-28 5:43 ` [PATCH v4 5/6] btrfs: Cleanup num_tolerated_disk_barrier_failures Qu Wenruo
2017-06-28 5:43 ` [PATCH v4 6/6] btrfs: Enhance missing device kernel message Qu Wenruo
2017-06-28 13:54 ` [PATCH v4 0/6] Chunk level degradable check David Sterba
2017-07-10 18:11 ` Dmitrii Tcvetkov
2017-07-13 0:50 ` David Sterba
2017-07-13 1:09 ` Adam Borowski
2017-07-13 12:12 ` Austin S. Hemmelgarn
2017-07-12 15:24 ` David Sterba
2017-07-12 23:53 ` Qu Wenruo
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=aebaca38-e283-17bf-c488-bb0d3ac96876@suse.com \
--to=nborisov@suse.com \
--cc=ahferroin7@gmail.com \
--cc=anand.jain@oracle.com \
--cc=demfloro@demfloro.ru \
--cc=dsterba@suse.cz \
--cc=kilobyte@angband.pl \
--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).