Hello,
while trying to initialize a btrfs RAID1 on my new NAS using LUKS
crypt-devices for each of the btrfs RAID devices, I have seen "random"
weirdness shortly after mkfs.
It seems to boil down to the problem that after mkfs.btrfs, some of the
/dev/dm-* nodes (as well as the corresponding /dev/mapper/* symlinks)
sometimes disappear. The RAID can be mounted at first but quickly shows
symptoms such as missing devices, or being unable to mount the second time.
I have tried to btrfs.mkfs -d raid1 -m raid1 using the /dev/dm-* and
/dev/mapper/* devices, but with similar results.
By best guess is that the fact that one UUID is given to multiple
separate devices confuses... something (udev or the like?), making nodes
appear, disappear or being re-ordered while mkfs is in progress, or
leading to unexpected things later at mount time.
Honestly, the idea of the same UUID being given to separate physical
devices scared me already when I first saw it. Could that actually be
the culprit here?
Best regards
Sebastian
--
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
