mkfs.btrfs -L LABEL -d raid1 -m raid1 /dev/sdd1 /dev/sde1
gdisk /dev/sdx
: one GPT partition over the whole diskmkfs.btrfs /dev/sdx1
mount /dev/sdx1 /mnt/data
rsync -a –info=progress2 /mnt/olddata /mnt/data
gdisk /dev/sdx
: one GPT partition spanning the whole diskbtrfs device add /dev/sdx1 /mnt/data
btrfs balance start -dconvert=raid0 -mconvert=raid1 /mnt/data
A write hole in a RAID1 occurs when a file is written while the device is disconnected, e.g. due to a power failure. If the metadata hasn't been written properly, the files may be lost even though the data seems to have been saved. The developers of Btrfs warn that their RAID5/6 code might be more susceptible to that issue and discourage the use of RAID5/6, even though some improvements have been made over the years.
This is hard to reproduce2 and can be partially mitigated by setting the metadata strategy to raid1c3 or higher.
gdisk /dev/sdx
: b → sdx-backupblkid /dev/sdx1
btrfs fi res
btrfs fi sh –raw /mnt/point
outputgdisk -l /dev/sdx1
outputgdisk /dev/sdx
: d → n → 1 → 2048 → 2048+size/Logical sector size → 8300 → x → c → PARTUUID → wbtrfs check /dev/sdx1
btrfs scrub start /mnt/point
(check with btrfs scrub status /mnt/point
There's a driver for Windows called WinBtrfs.