Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp887084pxx; Tue, 27 Oct 2020 03:05:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxp/AGFxHDKbqxzrwjPHY7KEHfXiGsgMJsFxwczej3KuQz7cxZ6EVTz0dKSBZ+7jMzQhso6 X-Received: by 2002:aa7:d496:: with SMTP id b22mr1431769edr.123.1603793103004; Tue, 27 Oct 2020 03:05:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603793102; cv=none; d=google.com; s=arc-20160816; b=Mait7m7ef77AHqZY7gdCkdK9nHcbJBxeey2H5ze6j4O7hsEG3ezs+3ngUgOWTtoYkE QwSxrHf3BN1pqB6NvSX3r3NWgaPO8xnjmXf78QYnZs7WfJQpab+a6vIk1Jwt5qZXauju rCtOZWWx5bPMwO0Y9p1MDybDIOJmmYhTW+jgplM+cxz2YvElLU3QScMrDBW3WqD1rHD/ qi9muL33OivHkGqoN/3naGqyYve++kWALt9WQNDTykyV+f8ko57cBANjjWoSyEjfBOua SS/rmzOrlcyAX2s4i2R2jgZcwUa9mxHV2FnDNj9wXhXFMUFZ5DMjUb28WFDHMVcwti/z f4gg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=lO9CcetBXrhDCID+8S1Jugtv1kfVRnbseDsxzbhDh90=; b=VPBZRWrnZE2GT7Q23FXaI5cR7k/7bjLAfxwvTZrUpejrEfGqk0F+W43+i1H7URDU6C wtDF4FVz8EF97JYNLcz0tFGnT92gZTOjrM7vf/kl58veYYx1RDStjSmNSMOjKLi+tDzJ H2ypXbvbtsqCGPAEhbpEs2UMYa1dVjMLtDbZHGzvIvAV6NnhOF2RlUNsTsW2n9deVpAM Wy9f2X0cXvzNHjdWh2kAKdnY7AB4n6Xa06h7dAoiVU3lyDa+DGlGnmGqkd4PHQVH/KXJ HG/o3z8V9VuLSWrCnnLNG5lpBcvgQqtEZKxCNn/gwu+NGYbdISNfv10FMLSX7zVgg9xg c0JQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=RtAaqPV6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z3si468538edq.407.2020.10.27.03.04.41; Tue, 27 Oct 2020 03:05:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=RtAaqPV6; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2437339AbgJ0ABh (ORCPT + 99 others); Mon, 26 Oct 2020 20:01:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:35522 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2411114AbgJZX4Y (ORCPT ); Mon, 26 Oct 2020 19:56:24 -0400 Received: from sasha-vm.mshome.net (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3BCBD20882; Mon, 26 Oct 2020 23:56:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1603756583; bh=ol2X9YMCmNw1ekZCMxAoxYUEXg/Cgz45jCCGj6GF47Y=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=RtAaqPV6q99K+SBDkRFZ7URzdbBIj34jtLfV9B2U7nYu0HPsqSxPcxi+2vcPGvtws BQo14QybGNmUHnM6z066ZE40BJoJmep8vlXj21C6nhc3gZMxjD4qwRiowZZrg6EBBx 6eOqH4ETZFHNZg6lPmBYj1jcDXWnDGkT3Bwst1io= From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Anand Jain , David Sterba , Sasha Levin , linux-btrfs@vger.kernel.org Subject: [PATCH AUTOSEL 5.4 56/80] btrfs: fix replace of seed device Date: Mon, 26 Oct 2020 19:54:52 -0400 Message-Id: <20201026235516.1025100-56-sashal@kernel.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20201026235516.1025100-1-sashal@kernel.org> References: <20201026235516.1025100-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Anand Jain [ Upstream commit c6a5d954950c5031444173ad2195efc163afcac9 ] If you replace a seed device in a sprouted fs, it appears to have successfully replaced the seed device, but if you look closely, it didn't. Here is an example. $ mkfs.btrfs /dev/sda $ btrfstune -S1 /dev/sda $ mount /dev/sda /btrfs $ btrfs device add /dev/sdb /btrfs $ umount /btrfs $ btrfs device scan --forget $ mount -o device=/dev/sda /dev/sdb /btrfs $ btrfs replace start -f /dev/sda /dev/sdc /btrfs $ echo $? 0 BTRFS info (device sdb): dev_replace from /dev/sda (devid 1) to /dev/sdc started BTRFS info (device sdb): dev_replace from /dev/sda (devid 1) to /dev/sdc finished $ btrfs fi show Label: none uuid: ab2c88b7-be81-4a7e-9849-c3666e7f9f4f Total devices 2 FS bytes used 256.00KiB devid 1 size 3.00GiB used 520.00MiB path /dev/sdc devid 2 size 3.00GiB used 896.00MiB path /dev/sdb Label: none uuid: 10bd3202-0415-43af-96a8-d5409f310a7e Total devices 1 FS bytes used 128.00KiB devid 1 size 3.00GiB used 536.00MiB path /dev/sda So as per the replace start command and kernel log replace was successful. Now let's try to clean mount. $ umount /btrfs $ btrfs device scan --forget $ mount -o device=/dev/sdc /dev/sdb /btrfs mount: /btrfs: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error. [ 636.157517] BTRFS error (device sdc): failed to read chunk tree: -2 [ 636.180177] BTRFS error (device sdc): open_ctree failed That's because per dev items it is still looking for the original seed device. $ btrfs inspect-internal dump-tree -d /dev/sdb item 0 key (DEV_ITEMS DEV_ITEM 1) itemoff 16185 itemsize 98 devid 1 total_bytes 3221225472 bytes_used 545259520 io_align 4096 io_width 4096 sector_size 4096 type 0 generation 6 start_offset 0 dev_group 0 seek_speed 0 bandwidth 0 uuid 59368f50-9af2-4b17-91da-8a783cc418d4 <--- seed uuid fsid 10bd3202-0415-43af-96a8-d5409f310a7e <--- seed fsid item 1 key (DEV_ITEMS DEV_ITEM 2) itemoff 16087 itemsize 98 devid 2 total_bytes 3221225472 bytes_used 939524096 io_align 4096 io_width 4096 sector_size 4096 type 0 generation 0 start_offset 0 dev_group 0 seek_speed 0 bandwidth 0 uuid 56a0a6bc-4630-4998-8daf-3c3030c4256a <- sprout uuid fsid ab2c88b7-be81-4a7e-9849-c3666e7f9f4f <- sprout fsid But the replaced target has the following uuid+fsid in its superblock which doesn't match with the expected uuid+fsid in its devitem. $ btrfs in dump-super /dev/sdc | egrep '^generation|dev_item.uuid|dev_item.fsid|devid' generation 20 dev_item.uuid 59368f50-9af2-4b17-91da-8a783cc418d4 dev_item.fsid ab2c88b7-be81-4a7e-9849-c3666e7f9f4f [match] dev_item.devid 1 So if you provide the original seed device the mount shall be successful. Which so long happening in the test case btrfs/163. $ btrfs device scan --forget $ mount -o device=/dev/sda /dev/sdb /btrfs Fix in this patch: If a seed is not sprouted then there is no replacement of it, because of its read-only filesystem with a read-only device. Similarly, in the case of a sprouted filesystem, the seed device is still read only. So, mark it as you can't replace a seed device, you can only add a new device and then delete the seed device. If replace is attempted then returns -EINVAL. Signed-off-by: Anand Jain Signed-off-by: David Sterba Signed-off-by: Sasha Levin --- fs/btrfs/dev-replace.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c index 196bd241e701a..34ddf2d75c1af 100644 --- a/fs/btrfs/dev-replace.c +++ b/fs/btrfs/dev-replace.c @@ -190,7 +190,7 @@ static int btrfs_init_dev_replace_tgtdev(struct btrfs_fs_info *fs_info, int ret = 0; *device_out = NULL; - if (fs_info->fs_devices->seeding) { + if (srcdev->fs_devices->seeding) { btrfs_err(fs_info, "the filesystem is a seed filesystem!"); return -EINVAL; } -- 2.25.1