On Tue, 2011-02-01 at 16:17 +0000, ingo wrote: > > you can put this just after the remounts: > > lsof -n | grep DEL > > sleep 10 > > *Lucid-amd64* > I did so (with new libc6 and upstart from Lucid-proposed installed) and found > something new: > it's the NFS which makes trouble. Portmap and statd are still running! > > (I just list the essential information here, as I took a screenshot, but > could upload the *.png as well.) > > init: Re-executing /sbin/init > mount: / is busy > portmap 445 daemon DEL REG 8,1 /lib/libnsl-2.11.1.so > " > /lib/libc-2.11.1.so > " > /lib/ld-2.11.1.so > rpc.statd 602 statd DEL REG 8,1 /lib/libnss_files-2.11.1.so > " > /lib/libnsl-2.11.1.so > " > /lib/libc-2.11.1.so > " > /lib/ld-2.11.1.so >
Ingo, thanks for the rapid feedback! I think this is actually a new bug against portmap caused by its migration to upstart. /etc/init.d/umountnfs.sh defines # Should-Stop: $network $portmap nfs-common And portmap actually does tell dh_installinit to stop after umountnfs: dh_installinit --name portmap -- start 43 S 2 3 4 5 . start 32 0 6 . stop 81 1 . But there is no way to codify that point in the shutdown into the upstart job, which I suspect is why it has no stop on. I believe the proper way to handle this is to have a matching event to remote-filesystems , unmounted-remote-filesystems, with which to stop on, and then have umountnfs.sh emit that. A more succinct method would be to simply add stop portmap 2>/dev/null || : to umountnfs.sh Either way, portmap should be responsible for shutting down at the right moment, and so I've opened bug #711425 against portmap. -- You received this bug notification because you are a member of Ubuntu Server Team, which is a direct subscriber. https://bugs.launchpad.net/bugs/672177 Title: libc6 upgrade causes umount to fail on shutdown because init cannot be restarted -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
