Package: cryptsetup-run Severity: minor We’ve got the same problem as https://superuser.com/q/1343150/255031 and https://www.linuxquestions.org/questions/debian-26/shutdown-hangs-at-stopping-remaining-crypto-disks-busy-4175548975/
On shutting down a system whose root filesystem lives on crypto, here indirectly via LVM, the shutdown process displays something like: Stopping remaining crypto disks...sda5_crypt (busy)... sda5_crypt busy… This takes a while (about a minute or so), then the shutdown continues. The cause is trivial: the root filesystem is still live, so the crypto disc cannot be deconfigured. Is there a way to tell cryptsetup to not warn about a busy device if the root filesystem resides on it, for example via a crypttab option? I only found options like noauto that do the exact contrary. Perhaps introducing a new option hasrootfs or something may be useful? Thanks in advance, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
