I should have added some more technical info. Here you go:
Arch Linux with systemd 233 Kernel linux-lts 4.9.27 btrfs-progs 4.10.2 Example session: root@nas> ls /dev/dm-* /dev/dm-0 /dev/dm-1 /dev/dm-2 /dev/dm-3 /dev/dm-4 root@nas> ls -l /dev/mapper total 0 lrwxrwxrwx 1 root root 7 May 11 22:30 backup -> ../dm-1 crw------- 1 root root 10, 236 May 11 22:30 control lrwxrwxrwx 1 root root 7 May 11 22:30 root -> ../dm-0 lrwxrwxrwx 1 root root 7 May 11 22:30 storage0 -> ../dm-2 lrwxrwxrwx 1 root root 7 May 11 22:30 storage1 -> ../dm-4 lrwxrwxrwx 1 root root 7 May 11 22:30 storage2 -> ../dm-3 root@nas> mkfs.btrfs -f -d raid1 -m raid1 /dev/dm-2 /dev/dm-3 /dev/dm-4 btrfs-progs v4.10.2 See http://btrfs.wiki.kernel.org for more information. Label: (null) UUID: a32b3106-678f-448f-ade9-c48cd41a7dae Node size: 16384 Sector size: 4096 Filesystem size: 10.92TiB Block group profiles: Data: RAID1 1.00GiB Metadata: RAID1 1.00GiB System: RAID1 8.00MiB SSD detected: no Incompat features: extref, skinny-metadata Number of devices: 3 Devices: ID SIZE PATH 1 3.64TiB /dev/dm-2 2 3.64TiB /dev/dm-3 3 3.64TiB /dev/dm-4 root@nas> ls /dev/dm-* /dev/dm-0 /dev/dm-1 /dev/dm-2 /dev/dm-4 Note that dm-3 is gone. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
