From: Nikolay Borisov <nborisov@suse.com>
To: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3/4] btrfs: include non-missing as a qualifier for the latest_bdev
Date: Fri, 4 Oct 2019 11:11:07 +0300 [thread overview]
Message-ID: <93c711f8-dc77-dcc2-52b0-fc46487ff16e@suse.com> (raw)
In-Reply-To: <1570175403-4073-4-git-send-email-anand.jain@oracle.com>
On 4.10.19 г. 10:50 ч., Anand Jain wrote:
> btrfs_free_extra_devids() reorgs fs_devices::latest_bdev
> to point to the bdev with greatest device::generation number.
> For a typical-missing device the generation number is zero so
> fs_devices::latest_bdev will never point to it.
>
> But if the missing device is due to alienating [1], then
> device::generation is not-zero and if it is >= to rest of
> device::generation in the list, then fs_devices::latest_bdev
> ends up pointing to the missing device and reports the error
> like this [2]
>
> [1]
> mkfs.btrfs -fq /dev/sdd && mount /dev/sdd /btrfs
> mkfs.btrfs -fq -draid1 -mraid1 /dev/sdb /dev/sdc
> sleep 3 # avoid racing with udev's useless scans if needed
> btrfs dev add -f /dev/sdb /btrfs
Hm, here I think the correct way is to refuse adding /dev/sdb to an
existing fs if it's detected to be part of a different one. I.e it
should require wipefs to be done.
>
> mount -o degraded /dev/sdc /btrfs1
>
> [2]
> mount: wrong fs type, bad option, bad superblock on /dev/sdc,
> missing codepage or helper program, or other error
>
> In some cases useful info is found in syslog - try
> dmesg | tail or so.
>
> kernel: BTRFS warning (device sdc): devid 1 uuid 072a0192-675b-4d5a-8640-a5cf2b2c704d is missing
> kernel: BTRFS error (device sdc): failed to read devices
> kernel: BTRFS error (device sdc): open_ctree failed
>
> Fix the root of the issue, by checking if the the device is not
> missing before it can be a contender for the fs_devices::latest_bdev
> title.
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> fs/btrfs/volumes.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 05ade8c7342b..6c42048ec099 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -1186,6 +1186,8 @@ void btrfs_free_extra_devids(struct btrfs_fs_devices *fs_devices, int step)
> &device->dev_state)) {
> if (!test_bit(BTRFS_DEV_STATE_REPLACE_TGT,
> &device->dev_state) &&
> + !test_bit(BTRFS_DEV_STATE_MISSING,
> + &device->dev_state) &&
> (!latest_dev ||
> device->generation > latest_dev->generation)) {
> latest_dev = device;
>
next prev parent reply other threads:[~2019-10-04 8:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 7:49 [PATCH 0/4] btrfs: fix issues due to alien device Anand Jain
2019-10-04 7:50 ` [PATCH 1/4] btrfs: drop useless goto in open_fs_devices Anand Jain
2019-10-04 8:12 ` Nikolay Borisov
2019-10-04 7:50 ` [PATCH 2/4] btrfs: delete identified alien device " Anand Jain
2019-10-04 8:18 ` Nikolay Borisov
2019-10-06 2:47 ` [PATCH v2 " Anand Jain
2019-10-06 11:44 ` Nikolay Borisov
2019-10-06 2:51 ` [PATCH " Anand Jain
2019-10-04 7:50 ` [PATCH 3/4] btrfs: include non-missing as a qualifier for the latest_bdev Anand Jain
2019-10-04 8:11 ` Nikolay Borisov [this message]
2019-10-04 9:08 ` [Not TLS] " Graham Cobb
2019-10-04 9:20 ` Nikolay Borisov
2019-10-04 7:50 ` [PATCH 4/4] btrfs: free alien device due to device add Anand Jain
2019-10-04 8:19 ` [PATCH 0/4] btrfs: fix issues due to alien device Nikolay Borisov
2019-10-07 9:42 ` 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=93c711f8-dc77-dcc2-52b0-fc46487ff16e@suse.com \
--to=nborisov@suse.com \
--cc=anand.jain@oracle.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 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).