Package: btrfs-progs Version: 5.10.1-1 Kernel version: 5.10.0-3-amd64 Steps to recreate: Create two volume groups: i.e. enuoda-blu, enuoda-red Create two logical volumes: i.e. enuoda-blu/lvol0, enuoda-red/lvol0 Create a btrfs filesystem on one logical volume and mount it: # mkfs.btrfs /dev/mapper/enuoda--blu-lvol0 # mount /dev/mapper/enuoda--blu-lvol0 /mnt/enuoda
Then try to add the second volume and fails: # btrfs device add -f /dev/mapper/enuoda-red-lvol0 /mnt/enuoda ERROR: error adding device 'dm-4': No such file or directory ^^^ HERE IT IS ^^^ No output in dmesg. (tested on raspberrypi with buster (kernel 5.10.11-v7+ btrfs-progs:5.10-1~bpo10+1), works flawlessly) Same results if the two logical volumes are in the same volume group. Instead, directly creating a btrfs filesystem over two logical volumes works fine: # mkfs.btrfs -f /dev/mapper/enuoda--blu-lvol0 /dev/mapper/enuoda--red-lvol0 btrfs-progs v5.10.1 See http://btrfs.wiki.kernel.org for more information. Label: (null) UUID: c5c64454-d05b-4ed2-b644-6ef84b87561b Node size: 16384 Sector size: 4096 Filesystem size: 20.00GiB Block group profiles: Data: single 8.00MiB Metadata: RAID1 256.00MiB System: RAID1 8.00MiB SSD detected: no Incompat features: extref, skinny-metadata Runtime features: Checksum: crc32c Number of devices: 2 Devices: ID SIZE PATH 1 10.00GiB /dev/mapper/enuoda--blu-lvol0 2 10.00GiB /dev/mapper/enuoda--red-lvol0
