On Do, 09.01.20 23:27, Mantas Mikulėnas (grawity@xxxxxxxxx) wrote: > On Thu, Jan 9, 2020 at 11:03 PM Phillip Susi <phill@xxxxxxxxxxxx> wrote: > > > Someone in #debian mentioned to me that they were getting some odd > > errors in their logs when running gparted. It seems that several years > > ago there was someone with a problem caused by systemd auto mounting > > filesystems in response to udev events triggered by gparted, and so as a > > workaround, gparted masks all mount units. Curtis Gedeck and I can't > > seem to figure out now, why this was needed because we can't seen to get > > systemd to automatically mount a filesystem just because it's device is > > hot plugged. Are there any circumstances under which systemd will mount > > a filesystem when it's device is hotplugged? > > > > Yes, in nearly all older systemd versions, if a fstab entry had 'auto' then > its generated .mount unit was automatically inserted into the corresponding > .device's Wants= list. (Which IMHO was quite useful with 'auto,nofail' > combined.) This was removed in systemd v242. Not removed, just changed to be conditioned by the x-systemd.device-bound fstab option (see other mail) Lennart -- Lennart Poettering, Berlin _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel