Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp1260127pxx; Tue, 27 Oct 2020 12:04:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy+66DMOwnqLfba0XxkyiVhgSVi5tXqJgEX3atBlVg9cmwS54sfZRWVnIM3800sFcHgbfIH X-Received: by 2002:a50:e79d:: with SMTP id b29mr3810079edn.57.1603825482365; Tue, 27 Oct 2020 12:04:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603825482; cv=none; d=google.com; s=arc-20160816; b=D60P592e9iJGTJAsUc1vwTlmwWFm+4W8QbeknRrEvg3maloXrOpuPAJUViUkcRVSdq HHDM71vRtSISKdPoZ5IB1n878qfyKspiy1NTso+QvvB+lNIVsFhxKtqtNWjPNViWc80K UDpN2P43ypE6zAzOXsGzlbMNYEseJy7gS/xkSGgGjWh242uxPK18akA1E9djap9rjyHC DaTO20kzI/xCOHI4RfeVZosOJNX70kXsyuz0QdxcMUJEN94dQA3pq7lxFKvjqOLVWvBI 2wH7n1xHtN/G3AMZUiVRJ2Rkdz8YzAmfQfzTMxoJCIgHtN7UqJpnWns0uyslnWfHW651 I0QQ== 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=KU1ZaJuMxT8XhLis9O56B5NMSqymnIOFcDHqQFT8JPQ=; b=R9Yto8Q/i22Uc9xfKD6DE4jdJ+iiVrwc+opXAiM1qoaWnlP5PZlBs6BIW38xbk4GpY TI9BpDvhYCxOHKpXUAw3udhyWKO0921Jt67wRdfHRts7feyNr0xko+T5FrRNYAf3LjHR 1zdRShKMNh+5/MER0nN0NehEG8lhQCja8DTC+r8Cue5ovuRnyeIyioT2IjV0Ak0varXb /X2IIQ4yLxxezZV3bQT7PMwpIR3YhKdMUwMclhNqGRfAHUUl37DUa0vkE4nXs/RgfZzA 6/xB7QehjfA6nGSWKQE5jOP0+P/6YWfyPfJaVdf7M8J9ogiCV3yUkJZZ/MAKrf5Pt1aH ihvQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=W046cHoS; 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 ay1si1571986edb.3.2020.10.27.12.04.19; Tue, 27 Oct 2020 12:04:42 -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=W046cHoS; 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 S2502088AbgJ0AjY (ORCPT + 99 others); Mon, 26 Oct 2020 20:39:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:51610 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2409336AbgJZXvM (ORCPT ); Mon, 26 Oct 2020 19:51:12 -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 D53E62075B; Mon, 26 Oct 2020 23:51:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1603756272; bh=ZQ4rUae0MFq+q+xuLJba7D1u85eRkZ30SW3jH8xmVcU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=W046cHoSC3Ov5I62XBdCKcxid8qUDspHjLObY70QsaiHQIz5fwFr5JNuPahqqXzx8 SwjQFyY4vFxYU/eoVxZvhBUAtG88pLNX0LpNsBG9XQY0QwW92Gqfwo4BqczYD23b0R PVSXppiq24XeIan7lLqYMBL5XkUVX3GBZxiA0F7U= 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.9 104/147] btrfs: fix replace of seed device Date: Mon, 26 Oct 2020 19:48:22 -0400 Message-Id: <20201026234905.1022767-104-sashal@kernel.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20201026234905.1022767-1-sashal@kernel.org> References: <20201026234905.1022767-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 e4a1c6afe35dc..0cb36746060da 100644 --- a/fs/btrfs/dev-replace.c +++ b/fs/btrfs/dev-replace.c @@ -230,7 +230,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