<div dir="ltr"><div dir="ltr">On Thu, Jan 9, 2020 at 11:03 PM Phillip Susi <<a href="mailto:phill@thesusis.net">phill@thesusis.net</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Someone in #debian mentioned to me that they were getting some odd<br>
errors in their logs when running gparted. It seems that several years<br>
ago there was someone with a problem caused by systemd auto mounting<br>
filesystems in response to udev events triggered by gparted, and so as a<br>
workaround, gparted masks all mount units. Curtis Gedeck and I can't<br>
seem to figure out now, why this was needed because we can't seen to get<br>
systemd to automatically mount a filesystem just because it's device is<br>
hot plugged. Are there any circumstances under which systemd will mount<br>
a filesystem when it's device is hotplugged?<br></blockquote><div><br></div><div>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.</div></div><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Mantas Mikulėnas</div></div></div>