[00:13] hallyn, a more canonical name was taken [00:32] The confusion exists with github.com/ubuntu/ \o/ [00:46] Unit193, that's the other half of the company we don't speak to =) [00:46] muahahahahhaha [00:51] * Unit193 makes note to give xnox a good sanity check. :> [00:55] hallyn: :) [01:03] Unit193: like an autopkgtest, when the sanity check always comes back negative, it doesn't do you much good === Whoopie_ is now known as Whoopie === sergiusens_ is now known as sergiusens [15:19] Can somebody help me understand what's going on in bug 991471? It still affects bionic and I'd like to see what I can do to get it fixed. IOW, how does the automatic mounting happen? [15:19] bug 991471 in udisks2 (Ubuntu) "multi-device btrfs filesystem automatically mounted once for each device" [Medium,Confirmed] https://launchpad.net/bugs/991471 [15:21] The ticket says udisks2, presumably driven by gvfs or some other gnome automounting component. You've asked before, so presumably read the ticket. What else is there to know? [15:22] Well, it's me who set the component to udisks2 ;-) [15:22] I'm not entirely sure that's correct, but seems like the most likely candidate. [15:23] Presumably reproducing the problem isn't too hard if you have a system you don't mind installing udisks2 on, and a usb stick. [15:23] What I'd like to know for example is why in the case of a 2-device btrfs the automounter mounts it twice. What is the command-line I can check where this goes astray. [15:24] Faux: I *am* affected by the problem [15:24] no need for a test system. [15:24] I imagine the automounter is very much "for device in new_devices; do mount $device /media/automounted$i; i=$((i+1)); done". [15:24] then the question is what populates $new_devices [15:26] I have to admit I simply don't know enough of what's going on under the hood. That's why I'm here to ask. [15:26] The fact that those devices just appeared on the system? I don't think this is the appropriate place to discuss it, nor do I know anything about udisks2. [15:26] a 10-device btrfs is still just a single FS and should be mounted only once [15:27] I have a multi-device btrfs here and mount using /etc/fstab and it works fine. :) [15:28] In the past I've experienced it that one additional mount was added every hour or so. You appear awfully non-chalant about this. I can tell you it's highly annoying. [15:28] Yes, multi-FS btrfs in /etc/fstab are excluded from the problem [15:28] But then again, they do not show up in nautilus, etc. as automounts anyhow. [15:29] I don't mean to be rude, but this is almost certainly the wrong place, and I'm the wrong person. [15:29] OK [15:29] What is a better place? [15:29] I've already asked ubuntu+1. And posed this question several times over the last few years. [15:30] somebody must know HOW automounting happens [15:30] that's all I'm trying to understand [15:32] Laibsch, it's just a property of btrfs, that all btrfs drives are added together to the total pool, no? [15:33] Laibsch, as in you cannot connected two sets of drives, with distict / disjoint btrfs pools and operate them separately. [15:33] not sure I get your question right, but other FS are also affected [15:33] xnox: No, you can have many btrfs filesystems made from many different partitions in a machine; it's not systemwide like that. [15:34] Laibsch, i don't see how any other FS is also affected. the bug is very btrfs specific, as far as I can tell. [15:35] or, the fact that generic functionality, doesn't work as expected with a special-case of advanced btrfs features. [15:37] I have to concede that in the bug tracker there is no mention of other FS, it's just something I seem to recall, but I've seen this for years now so I might be wrong [15:41] we used to have bugs with lvm snapshots being shown in nautilus over and over and over again, which was a bit ugly. that was fixed. but again, was specific to lvm features in that case. [15:42] what's a good place to discuss this? [18:21] xnox: Have you seen bug 1765724? [18:21] bug 1765724 in cryptsetup (Ubuntu) "Xenial -> Bionic - System fails to boot after upgrade -