From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs: Remove unneeded missing device number check
Date: Thu, 17 Sep 2015 17:43:13 +0800 [thread overview]
Message-ID: <55FA8B31.9080604@oracle.com> (raw)
In-Reply-To: <1442375031-18212-2-git-send-email-quwenruo@cn.fujitsu.com>
On 09/16/2015 11:43 AM, Qu Wenruo wrote:
> As we do per-chunk missing device number check at read_one_chunk() time,
> it's not needed to do global missing device number check.
>
> Just remove it.
However the missing device count, what we have during the remount is not
fine grained per chunk.
-----------
btrfs_remount
::
if (fs_info->fs_devices->missing_devices >
fs_info->num_tolerated_disk_barrier_failures &&
!(*flags & MS_RDONLY ||
btrfs_test_opt(root, DEGRADED))) {
btrfs_warn(fs_info,
"too many missing devices, writeable
remount is not allowed");
ret = -EACCES;
goto restore;
}
---------
Thanks, Anand
> Now btrfs can handle the following case:
> # mkfs.btrfs -f -m raid1 -d single /dev/sdb /dev/sdc
>
> Data chunk will be located in sdb, so we should be safe to wipe sdc
> # wipefs -a /dev/sdc
>
> # mount /dev/sdb /mnt/btrfs -o degraded
>
> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
> ---
> fs/btrfs/disk-io.c | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index 0b658d0..ac640ea 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -2947,14 +2947,6 @@ retry_root_backup:
> }
> fs_info->num_tolerated_disk_barrier_failures =
> btrfs_calc_num_tolerated_disk_barrier_failures(fs_info);
> - if (fs_info->fs_devices->missing_devices >
> - fs_info->num_tolerated_disk_barrier_failures &&
> - !(sb->s_flags & MS_RDONLY)) {
> - pr_warn("BTRFS: missing devices(%llu) exceeds the limit(%d), writeable mount is not allowed\n",
> - fs_info->fs_devices->missing_devices,
> - fs_info->num_tolerated_disk_barrier_failures);
> - goto fail_sysfs;
> - }
>
> fs_info->cleaner_kthread = kthread_run(cleaner_kthread, tree_root,
> "btrfs-cleaner");
>
next prev parent reply other threads:[~2015-09-17 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 3:43 [PATCH 1/2] btrfs: Do per-chunk degrade mode check at mount time Qu Wenruo
2015-09-16 3:43 ` [PATCH 2/2] btrfs: Remove unneeded missing device number check Qu Wenruo
2015-09-17 9:43 ` Anand Jain [this message]
2015-09-17 10:01 ` Qu Wenruo
2015-09-18 1:47 ` Anand Jain
2015-09-18 2:06 ` Qu Wenruo
2015-09-18 6:45 ` Anand Jain
2015-09-20 0:31 ` Qu Wenruo
2015-09-20 5:37 ` Anand Jain
2015-09-21 2:09 ` Qu Wenruo
2015-09-17 1:48 ` [PATCH 1/2] btrfs: Do per-chunk degrade mode check at mount time Qu Wenruo
2015-09-17 9:37 ` Anand Jain
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=55FA8B31.9080604@oracle.com \
--to=anand.jain@oracle.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).