[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
*** This bug is a duplicate of bug 1061639 *** https://bugs.launchpad.net/bugs/1061639 This is nice, but all you've done here is run through manually stopping a bunch of stuff, not necessarily in order. What we need to know is absolutely and only whether the shutdown completes properly and cleanly with the automated procedure, via upstart. In other words: - Does upstart correctly run through rc scripts at shutdown, running sendsigs somewhere along the way to kill all processes that are *not* spawned by upstart and that are *not* listed in /run/sendsigs.omit.d; - Does upstart correctly continue through its events, and properly stop dbus, which will trigger stopping network-manager and modemmanager. On other instances you're also removing a whole bunch of packages. It's impossible to know which is the real cause of the issue if too many variables change at once -- one package should be removed at a time to figure out what blocks shutdown, or one upstart service should be manually stopped before shutdown to see whether it affects the shutdown procedure. Regardless, please file a separate bug report if it hasn't already been done, with the very specific details about the shutdown procedure as it is *now*, after release, after the ifupdown fix, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
*** This bug is a duplicate of bug 1061639 *** https://bugs.launchpad.net/bugs/1061639 I have also seen the strange behaviour that modemmanager seems to initialize at shutdown. Not sure if it is fixed in the latest updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
*** This bug is a duplicate of bug 1061639 *** https://bugs.launchpad.net/bugs/1061639 I'm not sure, if this isn't perhaps a bigger issue. This is definitely NOT FIXED. But most users won't notice it (until it's too late and the filesystem becomes more and more inconsistent). Comment posted on: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1061639 Sorry for the additionally comment here. But I really want to raise awareness of this issue, because –at least for my installations- it is so critically bad. It has something to do with services (init-scripts), /etc/init.d/, networking. But it's not only dns-masq, because I added an additional killall -9 dnsmasqd; sync; sync; sleep 3 in /etc/init.d/umountfs, and it says no process: dnsmasq, and it makes no difference. Filesystem never gets unmounted cleanly. Thanks and happy bug fixing! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
*** This bug is a duplicate of bug 1061639 *** https://bugs.launchpad.net/bugs/1061639 I agree with Christian. Even though the unmount issues don't seem to happen on my testing machine anymore, shutting down still feels weird. Just shut down a 12.04 machine and compare it to a 12.10 machine. You'll just know that something is wrong. It hangs, it takes a long time, and for some people, it still causes harmful issues. And it's almost release time. Add this to the Amazon mess, and Ubuntu will have the worst publicity in years; if not ever. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
*** This bug is a duplicate of bug 1061639 *** https://bugs.launchpad.net/bugs/1061639 FINALLY worked! :) (for the first time ever with quantal!) I tried about 2 hours shutting down manually. Stopping, starting init scripts, networking etc. I found this only way, and it was to be done exactly in this order. Contra: I have not yet figured the problem out exactly. I think many commands are not mandatory. Now it would be the time to sort them out. I wrote a pseudo log file. Out of my bash history. I'm not an expert, but I really hope you get the idea: (NOTE: DONE BEFORE: sudo apt-get remove --purge modemmanager COMMENT: TESTED IT WITH REBOOT, DIDN'T DO ANYTHING GOOD OR BAD ITSELF) BOOT, FSCK ERROR MESSAGE (EXIT 1, ERRORS RESOLVED), BOOT CONTINUING... LIGTHDM CTRL+ALT+F2 LOGIN TERMINAL sudo service lightdm stop sudo service dbus stop COMMENT: THAT DID HANG FOR A WHILE, APPROX 5 SECONDS / THE SAME IF YOU STOP NETWORKING BEFORE DBUS, IT HANGS, KILLS DBUS, -- THIS ORDER IS BETTER sudo service dbus start sudo service dbus stop COMMENT: NOW BOTH STARTS AND STOPS VERY FAST AND CLEAN sudo service networking stop COMMENT: NETWORKING STOPPED FAST AND CLEANLY sudo service networking start COMMENT: THEORY: FOR CLEAN SHUTDOWN WE HAVE START/STOP YET AGAIN sudo service networking stop sudo service rsyslog stop sudo modprobe -r forcedeth bnep rfcomm bluetooth COMMENT: SOMETIMES FORCEDETH MODULES BRINGS EVERYONE IN TROUBLE. WHAT ABOUT FORCEDETH? AND I GOT SOME MESSAGES WITH BLUETOOTH MODULE, – WHICH I DON'T HAVE BTW –, SO UNLOADING IT FOR A CLEAN STATE, –– BUT DIDN'T HELPED WHEN ONLY DOING THIS sync sudo init 1 COMMENT: TAKES A WHILE, AND KILLING ALL REMAINING PROCESSES SAYS IT FAILED COMMENT: NOW WE'RE ROOT, SO NO SUDO. BUT I ADD IT FOR NO CONFUSION sudo service udev stop COMMENT: STILL THERE STILL GOING (I THINK THAT'S CORRECT). AND STOPS FAST AND CLEAN. sudo /etc/init.d/networking start COMMENT: AGAIN STARTING, BUT ONLY INIT.D, NOT USING SERVICE. IT SEEMS THAT STARTING/STOPPING THOSE SCRIPTS SOLVES OUR PROBLEM COMMENT: ...AND NOW STOPPING POSSIBLY ALL OF THEM sudo /etc/init.d/networking stop sudo /etc/init.d/network-manager stop sudo /etc/init.d/network-interface-security stop sudo /etc/init.d/network-interface-container stop sudo /etc/init.d/network-interface stop COMMENT: ALL STOPS FAST AND CLEAN, PROMPTS COMMENT: NEARLY DONE! NOW WE MAKE SURE, THAT FSCK IS FORCED TO RUN. IF ERRORS IT WILL SAY WAS NOT CLEANY UMOUNTED. RETURN/EXIT VALUE: [1], PRINTED ON SCREEN. IF NO ERROR IT WILL SAY WAS MOUNTED X TIMES, CHECK FORCED. RETURN VALUE: 0. NO EXIT/ERROR MESSAGE PRINTED, CLEAN; CONTINUING BOOT sudo tune2fs -c 1 /dev/sda1 #max mount counts to 1 sudo tune2fs -C 100 /dev/sda1 #make believe, it was mounted 100 times already, will trigger fsck on reboot COMMENT: DOING TESTING sudo lsof / sudo fuser / COMMENT: AHA! LSOF STILL SHOW 2 (TWO!) PROCESSES NTPD RUNNING. BETTER KILL THEM. HOWEVER, I DON'T THINK THEY ARE THE PROBLEM. BECAUSE IF I ONLY KILL THEM, WITHOUT ALL THE PROCEDURE EXACTLY(!) IN ORDER ABOVE, THEN IT DOESN'T HELP sudo killall -15 ntpd COMMENT: CHECKING sudo ps -e sudo lsmod COMMENT: LOOKS GOOD! sudo sync; sync; sync; sudo init 6 ***REBOOOT*** AND... == CLEAN FILESYSTEM! :-) WORKED! APPENDIX 01: LSOF / (quite before the end, but before ntpd killing) sudo lsof / COMMANDPID USER FD TYPE DEVICE SIZE/OFF NODE NAME init 1 root cwdDIR8,1 4096 2 / init 1 root rtdDIR8,1 4096 2 / init 1 root txtREG8,1 163144 5938 /sbin/init init 1 root memREG8,152152 5660 /lib/x86_64-linux-gnu/libnss_files-2.15.so init 1 root memREG8,147712 5664 /lib/x86_64-linux-gnu/libnss_nis-2.15.so init 1 root memREG8,197272 5654 /lib/x86_64-linux-gnu/libnsl-2.15.so init 1 root memREG8,135712 5656 /lib/x86_64-linux-gnu/libnss_compat-2.15.so init 1 root memREG8,1 135398 5691 /lib/x86_64-linux-gnu/libpthread-2.15.so init 1 root memREG8,1 1811160 5596 /lib/x86_64-linux-gnu/libc-2.15.so init 1 root memREG8,131784 5699 /lib/x86_64-linux-gnu/librt-2.15.so init 1 root memREG8,1 277448 5608 /lib/x86_64-linux-gnu/libdbus-1.so.3.7.2 init 1 root memREG8,138920 5647 /lib/x86_64-linux-gnu/libnih-dbus.so.1.0.0 init 1 root memREG8,196280 5649 /lib/x86_64-linux-gnu/libnih.so.1.0.0 init 1 root memREG8,1 149312 5574 /lib/x86_64-linux-gnu/ld-2.15.so kthreadd 2 root cwdDIR8,1 4096 2 / kthreadd 2 root rtdDIR8,1 4096 2 / ksoftirqd3 root cwdDIR8,1 4096 2 / ksoftirqd3 root rtdDIR8,1 4096 2 / migration6 root cwdDIR8,1 4096 2 / migration6 root rtdDIR8,1 4096 2 /
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
*** This bug is a duplicate of bug 1061639 *** https://bugs.launchpad.net/bugs/1061639 ** Attachment added: Text file of complete log/howto (see also appendices of lsof /, ps -e, lsmod) https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+attachment/3402055/+files/cleanshutdown_howto2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
After tonight's dbus updates, still no change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
*** This bug is a duplicate of bug 1061639 *** https://bugs.launchpad.net/bugs/1061639 Right; turns out this is more likely all caused by bug 1061639. Network- manager stops on stopping dbus; so of course it will never get to stopping if dbus doesn't get its own stop condition. Marking this bug as a duplicate of 1061639. ** This bug has been marked a duplicate of bug 1061639 Upstartification of /etc/init.d/networking has lost deconfiguring-networking event causing bad side-effects -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
Just a side note: when I only purge network-manager and network-manager- gnome, but leave dnsmasq-base installed, the slow shutdown bug is solved, but the unmount problem persists. So I'm not completely sure if it's entirely caused by network-manager, as it also seems to happen when network-manager is not installed at all. If it's actually caused by dbus, it still makes sense though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
Bug 740390 was fixed (which should cover the issues with unmounting). Can you confirm whether that properly corrects most of the issue? ** Changed in: network-manager (Ubuntu) Assignee: Mathieu Trudel-Lapierre (mathieu-tl) = (unassigned) ** Changed in: network-manager (Ubuntu) Status: In Progress = Incomplete ** Changed in: network-manager (Ubuntu) Importance: High = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
I've just installed the updates; and it doesn't make any difference for me. I also tried reinstalling network-manager, network-manager-gnome and dnsmasq-base, but still nothing. I'll try a clean install in VirtualBox tonight. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
Tested this in VirtualBox: Custom Xubuntu 12.10 installation (netinst with Xfce packages) - fully updated: not fixed Stock Ubuntu 12.10 installation (installed with ubiquity, unmodified) - fully updated: not fixed Stock Xubuntu 12.10 installation (installed with ubiquity, unmodified) - fully updated: not fixed Fresh custom Xubuntu 12.10 installation (latest netinst with Xfce packages) - fully updated (while installing): not fixed Tested this on my testing machine: Custom Xubuntu 12.10 installation (netinst with Xfce packages) - fully updated: not fixed Stock Xubuntu 12.10 installation (installed with ubiquity, unmodified) - fully updated: not fixed Fresh custom Xubuntu 12.10 installation (latest netinst with Xfce packages) - fully updated (while installing): not fixed In each and every case, purging dnsmasq-base solves all issues. Purging only network-manager only solves the long shutdown time, but not the unmounting issue. Am I really the only one noticing the huge increase in shutdown time compared to 12.04, and hasn't anyone else seen fsck show up in every dmesg log? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
I didn't try to reproduce yet, but I definitely believe there might be a problem; so I'll look into it. It's probably my fault too ;) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- 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
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
Needs looking at nm-dns-dnsmasq.c to make sure the daemon is properly shut down when NM stops, which might have been broken by the dbus patch. ** Changed in: dnsmasq (Ubuntu) Status: New = In Progress ** Changed in: dnsmasq (Ubuntu) Importance: Undecided = High ** Changed in: dnsmasq (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) ** Package changed: dnsmasq (Ubuntu) = network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Milestone: None = ubuntu-12.10 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- 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
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
I didn't try to reproduce yet, but I definitely believe there might be a problem; so I'll look into it. It's probably my fault too ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
Needs looking at nm-dns-dnsmasq.c to make sure the daemon is properly shut down when NM stops, which might have been broken by the dbus patch. ** Changed in: dnsmasq (Ubuntu) Status: New = In Progress ** Changed in: dnsmasq (Ubuntu) Importance: Undecided = High ** Changed in: dnsmasq (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) ** Package changed: dnsmasq (Ubuntu) = network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Milestone: None = ubuntu-12.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
Possibly dupe, probably related https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1058517 . There, my experience in a cloud-image was dbus update caused the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058987 Title: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
