Linux Btrfs filesystem development
 help / color / mirror / Atom feed
* Creating btrfs RAID on LUKS devs makes devices disappear
@ 2017-05-11 20:17 Ochi
  2017-05-11 20:36 ` Ochi
  0 siblings, 1 reply; 11+ messages in thread
From: Ochi @ 2017-05-11 20:17 UTC (permalink / raw)
  To: linux-btrfs

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

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2017-05-13 18:51 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-05-11 20:17 Creating btrfs RAID on LUKS devs makes devices disappear Ochi
2017-05-11 20:36 ` Ochi
2017-05-11 22:24   ` Chris Murphy
2017-05-11 23:24     ` Ochi
2017-05-12 11:25       ` Austin S. Hemmelgarn
2017-05-12 13:54         ` Ochi
2017-05-12 14:11           ` Austin S. Hemmelgarn
2017-05-12 17:07       ` Chris Murphy
2017-05-13  7:29         ` Andrei Borzenkov
2017-05-13 15:28           ` Ochi
2017-05-13 18:51             ` Andrei Borzenkov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox