It is not possible to write a super block copy in sequential write required
zones as this prevents in-place updates required for super blocks. This
patch limits super block possible locations to zones accepting random
writes. In particular, the zone containing the first block of the device or
partition being formatted must accept random writes.
Signed-off-by: Naohiro Aota <naota@xxxxxxxxx>
---
disk-io.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/disk-io.c b/disk-io.c
index 26e4f6e9..127d8cf4 100644
--- a/disk-io.c
+++ b/disk-io.c
@@ -1523,6 +1523,7 @@ static int write_dev_supers(struct btrfs_fs_info *fs_info,
struct btrfs_super_block *sb,
struct btrfs_device *device)
{
+ struct btrfs_zone_info *zinfo = &device->zinfo;
u64 bytenr;
u32 crc;
int i, ret;
@@ -1534,6 +1535,11 @@ static int write_dev_supers(struct btrfs_fs_info *fs_info,
BTRFS_SUPER_INFO_SIZE - BTRFS_CSUM_SIZE);
btrfs_csum_final(crc, &sb->csum[0]);
+ if (!zone_is_random_write(zinfo, fs_info->super_bytenr)) {
+ ret = -EIO;
+ goto write_err;
+ }
+
/*
* super_copy is BTRFS_SUPER_INFO_SIZE bytes and is
* zero filled, we can use it directly
@@ -1550,6 +1556,8 @@ static int write_dev_supers(struct btrfs_fs_info *fs_info,
bytenr = btrfs_sb_offset(i);
if (bytenr + BTRFS_SUPER_INFO_SIZE > device->total_bytes)
break;
+ if (!zone_is_random_write(zinfo, bytenr))
+ continue;
btrfs_set_super_bytenr(sb, bytenr);
--
2.18.0
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
