diff options
| author | Anand Jain <anand.jain@oracle.com> | 2022-08-12 13:32:19 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-08-31 18:15:22 +0300 |
| commit | dcac6293f57136370a6f2016346f7c134fdf005d (patch) | |
| tree | a080235046b74bbf7d572159749c7b574f8449ee /net/psample/psample.c | |
| parent | b2d352ed4d489f9fdfe5caf7d5e62bd2c310f0a8 (diff) | |
| download | linux-dcac6293f57136370a6f2016346f7c134fdf005d.tar.xz | |
btrfs: add info when mount fails due to stale replace target
commit f2c3bec215694fb8bc0ef5010f2a758d1906fc2d upstream.
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/psample/psample.c')
0 files changed, 0 insertions, 0 deletions