On 2019/9/25 上午9:26, Chris Murphy wrote: > kernel 5.3.0-1.fc31.x86_64 > btrfs-progs-5.2.1-1.fc31.x86_64 > > sudo btrfs balance start -dconvert=single,soft / > ERROR: error during balancing '/': Invalid argument > There may be more info in syslog - try dmesg | tail > $ sudo btrfs balance start -dconvert=single / > ERROR: error during balancing '/': Invalid argument > There may be more info in syslog - try dmesg | tail > > > [372342.643440] BTRFS error (device sdb3): balance: invalid convert > data profile single > [372378.271689] BTRFS error (device sdb3): balance: invalid convert > data profile single > > Huh? I had just today accidentally started converting data to DUP. I > had intended to change metadata to DUP. I cancelled the data DUP > convert pretty early on. But now I appear stuck. Oh, this indeed looks like a bug, even with -f, it still fails on v5.3 kernel. I'll take a look into this bug. Thanks for the report, Qu > > $ sudo btrfs fi us / > Overall: > Device size: 25.00GiB > Device allocated: 19.57GiB > Device unallocated: 5.43GiB > Device missing: 0.00B > Used: 11.15GiB > Free (estimated): 7.82GiB (min: 5.52GiB) > Data ratio: 1.08 > Metadata ratio: 2.00 > Global reserve: 43.34MiB (used: 0.00B) > > Data,single: Size:11.01GiB, Used:8.98GiB > /dev/sdb3 11.01GiB > > Data,DUP: Size:1.00GiB, Used:508.62MiB > /dev/sdb3 2.00GiB > > Metadata,DUP: Size:3.25GiB, Used:603.25MiB > /dev/sdb3 6.50GiB > > System,DUP: Size:32.00MiB, Used:32.00KiB > /dev/sdb3 64.00MiB > > Unallocated: > /dev/sdb3 5.43GiB > $ sudo btrfs balance start -v -dconvert=single,soft / > Dumping filters: flags 0x1, state 0x0, force is off > DATA (flags 0x300): converting, target=281474976710656, soft is on > ERROR: error during balancing '/': Invalid argument > There may be more info in syslog - try dmesg | tail > $ sudo btrfs balance start -v -f -dconvert=single,soft / > Dumping filters: flags 0x9, state 0x0, force is on > DATA (flags 0x300): converting, target=281474976710656, soft is on > ERROR: error during balancing '/': Invalid argument > There may be more info in syslog - try dmesg | tail > $ sudo btrfs insp dump-s /dev/sdb3 > superblock: bytenr=65536, device=/dev/sdb3 > --------------------------------------------------------- > csum_type 0 (crc32c) > csum_size 4 > csum 0xabe229b9 [match] > bytenr 65536 > flags 0x1 > ( WRITTEN ) > magic _BHRfS_M [match] > fsid 3d93d834-ab33-40d1-8468-26fdc3eac4e0 > metadata_uuid 3d93d834-ab33-40d1-8468-26fdc3eac4e0 > label fedoraFIT > generation 96541 > root 18306990080 > sys_array_size 129 > chunk_root_generation 96449 > root_level 0 > chunk_root 18141446144 > chunk_root_level 0 > log_root 0 > log_root_transid 0 > log_root_level 0 > total_bytes 26843545600 > bytes_used 10804428800 > sectorsize 4096 > nodesize 32768 > leafsize (deprecated) 32768 > stripesize 4096 > root_dir 6 > num_devices 1 > compat_flags 0x0 > compat_ro_flags 0x3 > ( FREE_SPACE_TREE | > FREE_SPACE_TREE_VALID ) > incompat_flags 0x171 > ( MIXED_BACKREF | > COMPRESS_ZSTD | > BIG_METADATA | > EXTENDED_IREF | > SKINNY_METADATA ) > cache_generation 7 > uuid_tree_generation 86563 > dev_item.uuid f695e038-833e-4600-9a0c-0a13fb4d9f0e > dev_item.fsid 3d93d834-ab33-40d1-8468-26fdc3eac4e0 [match] > dev_item.type 0 > dev_item.total_bytes 26843545600 > dev_item.bytes_used 21021851648 > dev_item.io_align 4096 > dev_item.io_width 4096 > dev_item.sector_size 4096 > dev_item.devid 1 > dev_item.dev_group 0 > dev_item.seek_speed 0 > dev_item.bandwidth 0 > dev_item.generation 0 > $ > > >
Attachment:
signature.asc
Description: OpenPGP digital signature
