diff options
| author | Anand Jain <anand.jain@oracle.com> | 2022-08-12 18:32:19 +0800 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2022-08-23 22:15:21 +0200 |
| commit | f2c3bec215694fb8bc0ef5010f2a758d1906fc2d (patch) | |
| tree | 39bd1d6eca0b5e4998473ec60284b1718047496d | |
| parent | 59a3991984dbc1fc47e5651a265c5200bd85464e (diff) | |
| download | linux-stable-f2c3bec215694fb8bc0ef5010f2a758d1906fc2d.tar.gz linux-stable-f2c3bec215694fb8bc0ef5010f2a758d1906fc2d.tar.bz2 linux-stable-f2c3bec215694fb8bc0ef5010f2a758d1906fc2d.zip | |
btrfs: add info when mount fails due to stale replace target
If the replace target device reappears after the suspended replace is
cancelled, it blocks the mount operation as it can't find the matching
replace-item in the metadata. As shown below,
BTRFS error (device sda5): replace devid present without an active replace item
To overcome this situation, the user can run the command
btrfs device scan --forget <replace target device>
and try the mount command again. And also, to avoid repeating the issue,
superblock on the devid=0 must be wiped.
wipefs -a device-path-to-devid=0.
This patch adds some info when this situation occurs.
Reported-by: Samuel Greiner <samuel@balkonien.org>
Link: https://lore.kernel.org/linux-btrfs/b4f62b10-b295-26ea-71f9-9a5c9299d42c@balkonien.org/T/
CC: stable@vger.kernel.org # 5.0+
Signed-off-by: Anand Jain <anand.jain@oracle.com>
Signed-off-by: David Sterba <dsterba@suse.com>
| -rw-r--r-- | fs/btrfs/dev-replace.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c index b1cddef87cd3..41cddd3ff059 100644 --- a/fs/btrfs/dev-replace.c +++ b/fs/btrfs/dev-replace.c @@ -165,7 +165,7 @@ no_valid_dev_replace_entry_found: */ if (btrfs_find_device(fs_info->fs_devices, &args)) { btrfs_err(fs_info, - "replace devid present without an active replace item"); +"replace without active item, run 'device scan --forget' on the target device"); ret = -EUCLEAN; } else { dev_replace->srcdev = NULL; |