Re: Creating btrfs RAID on LUKS devs makes devices disappear

13.05.2017 18:28, Ochi пишет: > Hello, > > okay, I think I now have a repro that is stupidly simple, I'm not even > sure if I overlook something here. No multi-device btrfs involved, but > notably it does happen with btrfs, but not with e.g. ext4. > I could not reproduce it with single device

Re: Creating btrfs RAID on LUKS devs makes devices disappear

Hello, okay, I think I now have a repro that is stupidly simple, I'm not even sure if I overlook something here. No multi-device btrfs involved, but notably it does happen with btrfs, but not with e.g. ext4. [Sidenote: At first I thought it had to do with systemd-cryptsetup opening multiple

Re: Creating btrfs RAID on LUKS devs makes devices disappear

12.05.2017 20:07, Chris Murphy пишет: > On Thu, May 11, 2017 at 5:24 PM, Ochi wrote: >> Hello, >> >> here is the journal.log (I hope). It's quite interesting. I rebooted the >> machine, performed a mkfs.btrfs on dm-{2,3,4} and dm-3 was missing >> afterwards (around timestamp 66.*).

Re: Creating btrfs RAID on LUKS devs makes devices disappear

On Thu, May 11, 2017 at 5:24 PM, Ochi wrote: > Hello, > > here is the journal.log (I hope). It's quite interesting. I rebooted the > machine, performed a mkfs.btrfs on dm-{2,3,4} and dm-3 was missing > afterwards (around timestamp 66.*). However, I then logged into the machine >

Re: Creating btrfs RAID on LUKS devs makes devices disappear

On 2017-05-12 09:54, Ochi wrote: On 12.05.2017 13:25, Austin S. Hemmelgarn wrote: On 2017-05-11 19:24, Ochi wrote: Hello, here is the journal.log (I hope). It's quite interesting. I rebooted the machine, performed a mkfs.btrfs on dm-{2,3,4} and dm-3 was missing afterwards (around timestamp

Re: Creating btrfs RAID on LUKS devs makes devices disappear

On 12.05.2017 13:25, Austin S. Hemmelgarn wrote: On 2017-05-11 19:24, Ochi wrote: Hello, here is the journal.log (I hope). It's quite interesting. I rebooted the machine, performed a mkfs.btrfs on dm-{2,3,4} and dm-3 was missing afterwards (around timestamp 66.*). However, I then logged into

Re: Creating btrfs RAID on LUKS devs makes devices disappear

On 2017-05-11 19:24, Ochi wrote: Hello, here is the journal.log (I hope). It's quite interesting. I rebooted the machine, performed a mkfs.btrfs on dm-{2,3,4} and dm-3 was missing afterwards (around timestamp 66.*). However, I then logged into the machine from another terminal (around timestamp

Re: Creating btrfs RAID on LUKS devs makes devices disappear

Hello, here is the journal.log (I hope). It's quite interesting. I rebooted the machine, performed a mkfs.btrfs on dm-{2,3,4} and dm-3 was missing afterwards (around timestamp 66.*). However, I then logged into the machine from another terminal (around timestamp 118.*) which triggered

Re: Creating btrfs RAID on LUKS devs makes devices disappear

journalctl -b -o short-monotonic > journal.log And then attached the log, hopefully it's small enough to be accepted by the list server (should be). If that's not revealing it might be necessary to reboot with rd.udev.debug but start with the simple case first and see if that reveals what's going

Creating btrfs RAID on LUKS devs makes devices disappear

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

Creating btrfs RAID on LUKS devs makes devices disappear

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