Re: Can I see what device was used to mount btrfs?

03.05.2017 21:43, Chris Murphy пишет: > If I understand the bug report correctly, the user specifies mounting > by label which then systemd is converting into /dev/dm-0 (because it's > a two LUKS devices Btrfs volume). > No, that's not the problem. The actual reason for report is that systemd

Re: Can I see what device was used to mount btrfs?

qemu-kvm (Fedora 26 pre-beta guest and host) systemd-233-3.fc26.x86_64 kernel-4.11.0-0.rc8.git0.1.fc26.x86_64 The guest installed OS uses ext4, and boot parameters rd.udev.debug systemd.log_level=debug so we can see the entirety of Btrfs device discovery and module loading. Using virsh I can hot

Re: Can I see what device was used to mount btrfs?

Chris Murphy posted on Wed, 03 May 2017 12:43:36 -0600 as excerpted: > If I understand the bug report correctly, the user specifies mounting by > label which then systemd is converting into /dev/dm-0 (because it's a > two LUKS devices Btrfs volume). > > Why not convert the fstab mount by label

Re: Can I see what device was used to mount btrfs?

On 2017-05-03 14:12, Andrei Borzenkov wrote: 03.05.2017 14:26, Austin S. Hemmelgarn пишет: On 2017-05-02 15:50, Goffredo Baroncelli wrote: On 2017-05-02 20:49, Adam Borowski wrote: It could be some daemon that waits for btrfs to become complete. Do we have something? Such a daemon would

Re: Can I see what device was used to mount btrfs?

If I understand the bug report correctly, the user specifies mounting by label which then systemd is converting into /dev/dm-0 (because it's a two LUKS devices Btrfs volume). Why not convert the fstab mount by label request, into a /dev/by-uuid/ path; and then systemd calls mount with -u,--uuid

Re: Can I see what device was used to mount btrfs?

03.05.2017 14:26, Austin S. Hemmelgarn пишет: > On 2017-05-02 15:50, Goffredo Baroncelli wrote: >> On 2017-05-02 20:49, Adam Borowski wrote: It could be some daemon that waits for btrfs to become complete. Do we have something? >>> Such a daemon would also have to read the chunk tree.

Re: Can I see what device was used to mount btrfs?

On 2017-05-02 22:15, Kai Krakow wrote: >> For example, it would be possible to implement a sane check that >> prevent to mount a btrfs filesystem if two devices exposes the same >> UUID... > Ideally, the btrfs wouldn't even appear in /dev until it was assembled > by udev. But apparently that's

Re: Can I see what device was used to mount btrfs?

On 2017-05-02 16:15, Kai Krakow wrote: Am Tue, 2 May 2017 21:50:19 +0200 schrieb Goffredo Baroncelli : On 2017-05-02 20:49, Adam Borowski wrote: It could be some daemon that waits for btrfs to become complete. Do we have something? Such a daemon would also have to read

Re: Can I see what device was used to mount btrfs?

On 2017-05-02 15:50, Goffredo Baroncelli wrote: On 2017-05-02 20:49, Adam Borowski wrote: It could be some daemon that waits for btrfs to become complete. Do we have something? Such a daemon would also have to read the chunk tree. I don't think that a daemon is necessary. As proof of

Re: Can I see what device was used to mount btrfs?

On Tue, May 02, 2017 at 10:15:06PM +0200, Kai Krakow wrote: > Ideally, the btrfs wouldn't even appear in /dev until it was assembled > by udev. But apparently that's not the case, and I think this is where > the problems come from. I wish, btrfs would not show up as device nodes > in /dev that the

Re: Can I see what device was used to mount btrfs?

Am Tue, 2 May 2017 21:50:19 +0200 schrieb Goffredo Baroncelli : > On 2017-05-02 20:49, Adam Borowski wrote: > >> It could be some daemon that waits for btrfs to become complete. > >> Do we have something? > > Such a daemon would also have to read the chunk tree. > > I

Re: Can I see what device was used to mount btrfs?

On 2017-05-02 20:49, Adam Borowski wrote: >> It could be some daemon that waits for btrfs to become complete. Do we >> have something? > Such a daemon would also have to read the chunk tree. I don't think that a daemon is necessary. As proof of concept, in the past I developed a mount helper

Re: Can I see what device was used to mount btrfs?

On Tue, May 02, 2017 at 05:19:34PM +0300, Andrei Borzenkov wrote: > On Tue, May 2, 2017 at 4:58 PM, Adam Borowski wrote: > > On Sun, Apr 30, 2017 at 08:47:43AM +0300, Andrei Borzenkov wrote: > >> systemd waits for the final device that makes btrfs complete and mounts > >> it

Re: Can I see what device was used to mount btrfs?

On Tue, May 2, 2017 at 4:58 PM, Adam Borowski wrote: > On Sun, Apr 30, 2017 at 08:47:43AM +0300, Andrei Borzenkov wrote: >> I'm chasing issue with btrfs mounts under systemd >> (https://github.com/systemd/systemd/issues/5781) - to summarize, systemd >> waits for the final

Re: Can I see what device was used to mount btrfs?

On Sun, Apr 30, 2017 at 08:47:43AM +0300, Andrei Borzenkov wrote: > I'm chasing issue with btrfs mounts under systemd > (https://github.com/systemd/systemd/issues/5781) - to summarize, systemd > waits for the final device that makes btrfs complete and mounts it using > this device name. Systemd

Re: Can I see what device was used to mount btrfs?

On 04/30/2017 01:47 PM, Andrei Borzenkov wrote: I'm chasing issue with btrfs mounts under systemd (https://github.com/systemd/systemd/issues/5781) - to summarize, systemd waits for the final device that makes btrfs complete and mounts it using this device name. But in

Can I see what device was used to mount btrfs?

I'm chasing issue with btrfs mounts under systemd (https://github.com/systemd/systemd/issues/5781) - to summarize, systemd waits for the final device that makes btrfs complete and mounts it using this device name. But in /proc/self/mountinfo we actually see another device name. Due to