| |||||||||||||
Poettering: systemd for Administrators, Part XVIII (controllers)Poettering: systemd for Administrators, Part XVIII (controllers)Posted Nov 2, 2012 14:53 UTC (Fri) by knobunc (subscriber, #4678)In reply to: Poettering: systemd for Administrators, Part XVIII (controllers) by intgr Parent article: Poettering: systemd for Administrators, Part XVIII (controllers)
My only complaint with systemd is that I can't work out how to tell it to unmount and unlock a filesystem so I can fsck it.
I have an external SATA drive that I use for backups. Occasionally I have need to do:
However, the fsck fails because systemd has locked the device.
I have tried systemd stop of various unit names, but have never found the right one to make systemd not hold a lock on the device.
(Log in to post comments)
Poettering: systemd for Administrators, Part XVIII (controllers) Posted Nov 2, 2012 15:22 UTC (Fri) by raven667 (subscriber, #5198) [Link]
lsof might be your friend here to identify what is touching the device.
Poettering: systemd for Administrators, Part XVIII (controllers) Posted Nov 2, 2012 15:45 UTC (Fri) by knobunc (subscriber, #4678) [Link]
It did. It is process 1 (i.e. systemd). That's why I need to tell systemd to release it...
Poettering: systemd for Administrators, Part XVIII (controllers) Posted Nov 2, 2012 16:45 UTC (Fri) by rahulsundaram (subscriber, #21946) [Link]
file a bug report
|
|||||||||||||