[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
** Changed in: linux (Ubuntu) Status: Invalid => Incomplete ** Changed in: upstart Status: Invalid => Confirmed ** Changed in: upstart (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: upstart Status: Confirmed => Invalid ** Changed in: upstart (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Looks like bug #1169614 was finally fixed. But there's one more bug which cause same problem: bug #1307008 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
** Changed in: network-manager (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
14.04 — it's still a problem (dhclient issue). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Lennert of systemd refers to this bug on google+. He outlines a fix for the simple case: https://plus.google.com/115547683951727699051/posts/LjkLwkeDiLc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
This does seem to be getting kind of embarassing. With modern journalled filesystems on relatively straightforward hardware configs an unclean shutdown shouldn't be the end of the world (after all, power failures can happen), but it's not nice either. Unfortunately we also seem to have a hell of a lot of noise on Launchpad about this, people conflating different issues and causes, not reading previous posts properly, etc., etc. I'll be upgrading to 14.04 from 12.04 for main machines when it comes out, if the problem's still present then I will have another look. Last time I did, my own problems were caused by dhclient and ureadahead.. I can't remember which if any of those have now been fixed. If nothing else, pushing those fixes out will show if there are other outstanding shutdown problems affecting a lot of users. On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote: Lennert of systemd refers to this bug on google+. He outlines a fix for the simple case: https://plus.google.com/115547683951727699051/posts/LjkLwkeDiLc -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote: Lennert of systemd refers to this bug on google+. He outlines a fix for the simple case: The fix he outlines is not for this bug. It's not for a bug we have in upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of all of upstart's library dependencies, which are finite and accounted for. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Excerpts from Steve Langasek's message of 2014-01-22 16:51:06 UTC: On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote: Lennert of systemd refers to this bug on google+. He outlines a fix for the simple case: The fix he outlines is not for this bug. It's not for a bug we have in upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of all of upstart's library dependencies, which are finite and accounted for. I feel like he outlined two bugs. That one, I agree, is handled and meh. The other one is the one that would sweep up the mess we occasionally see when something misbehaves. I'd like to see Ubuntu's shutdown do more to protect against that failure mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On Wed, Jan 22, 2014 at 05:11:03PM -, Clint Byrum wrote: The other one is the one that would sweep up the mess we occasionally see when something misbehaves. I'd like to see Ubuntu's shutdown do more to protect against that failure mode. I would, too, but I don't agree that the method he proposes actually does this. Killing processes and unmounting devices in a loop is basically what we do already; the key difference is that some filesystems - potentially even including the root filesystem - may require additional daemon processes for their operation. This is the case for example if you have network filesystems mounted and are using NetworkManager, or if you use gss-encrypted NFS, or iscsi. So kill all processes and unmount all filesystems in a loop is not a reliable shutdown mechanism, it just moves the problem cases somewhere that Lennart apparently isn't seeing them. One of the problems we've seen repeatedly with trying to get clean shutdown involves NetworkManager's child processes *being* killed while they're still needed as part of managing the network. This is not a bug that's fixed by killing more processes. There may be other failure scenarios that need to be addressed. Part of the problem has been a lack of information about what's actually holding the root filesystem open in these cases. There's a pending merge proposal on sysvinit that should help us gather this information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Steve Dodd: Last time I did, my own problems were caused by dhclient and ureadahead.. It is not an ureadahead issue, it is an extra fork in upstart to launch shell for ureadahead if more than one partition mounted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On 01/22/2014 05:51 PM, Steve Langasek wrote: On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote: Lennert of systemd refers to this bug on google+. He outlines a fix for the simple case: The fix he outlines is not for this bug. It's not for a bug we have in upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of all of upstart's library dependencies, which are finite and accounted for. Why shouldn't switching to an independent file system (tmpfs/initramfs) and shutdown-init-process not help? That way you can kill all processes without exceptions. You can even entirely unmount the old root, no need for remounting it read-only anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On Wed, Jan 22, 2014 at 04:13:19PM -, Max wrote: Steve Dodd: Last time I did, my own problems were caused by dhclient and ureadahead.. It is not an ureadahead issue, it is an extra fork in upstart to launch shell for ureadahead if more than one partition mounted. Yes, I know - I was summarizing! On Wed, Jan 22, 2014 at 04:51:06PM -, Steve Langasek wrote: On Wed, Jan 22, 2014 at 09:19:13AM -, Benny wrote: Lennert of systemd refers to this bug on google+. He outlines a fix for the simple case: The fix he outlines is not for this bug. It's not for a bug we have in upstart in Ubuntu at all; we already reliably ensure telinit u on upgrade of all of upstart's library dependencies, which are finite and accounted for. Good to know, thank you. On Wed, Jan 22, 2014 at 06:21:52PM -, Steve Langasek wrote: [..] There may be other failure scenarios that need to be addressed. Part of the problem has been a lack of information about what's actually holding the root filesystem open in these cases. There's a pending merge proposal on sysvinit that should help us gather this information. I had been going to suggest this a while back - automated apport reporting of unclean shutdowns, with as much cause information as possible? I will try to do something constructive like boot into trusty and make sure my personal issues have been resolved (I've not looked at this for a few months.) I'm updating my images as we speak. Steve -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
In my case it's a dhclient process that likely respawns and prevents remount to read-only of root fs, due to a lease file opened for writing under /var/lib/NetworkManager/.. Result is unclean shutdown and recovery of dirty root file system on next boot. Attaching lsof output obtained just before call to umount in /etc/init.d/umountroot. As far as I can see, the only process having a regular file opened for writing on the root file system is dhclient: dhclient 1317 root4w REG8,5 578 530637 /var/lib/NetworkManager/dhclient-90ac51b1-a118-416f-a126-0ad83a2c7b9c-eth0.lease Clean Ubuntu 13.10 installation. This has certainly become an annoying and long lasting bug now. ** Attachment added: Output of lsof just before remount,ro of / https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3945966/+files/lsof.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I'd guess patch in bug 1169614 would help in my case (dhclient process). Any progress on evaluating and possibly including the patch provided in that bug ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
You are definivly right in that case a bug is allready opened(Bug #1073433 ) as i writing a comment to it The normal user wants a clean shutdown or reboot and as I wrote its a dirty hack until this problem is resolved by the maintainers we know the schutdown process isn't working correctly as i can see 154 comments on this issue and the @S60umountroot proccess is definitivly just before reboot/shutdown process and as i understand it in the right way @S20sendsigs should stop all running (upstart) processes after that we can @S31umountnfs.sh which is run before @S40umountfs which runs before @S60umountroot which expects that there are no more running processes (or open files)(otherwise we can't remount or unmount) left and at last runs (on a normal system nothing is between them) @S90reboot if there ane running processes at that moment that root is remountet or unmounted at shutdown or halt then fsck will complain on next boot. you could check with adding /bin/ps aux /ps_schutdown.log just before line 86 in the /etc/rc6/@S60umountroot script as you can see then there are running processes just before the umount happens. sometimes it is NM(with dhcpclient and dnsmasq etc) but not always i tried even adding a sleep 60 there to give the runnings some time to end but that wasn't working either because of the respawning ones an killall5 -9 at that point shoulndt hurt because nfs and fs(tmpfs,run and so on) should be allready unmounted plymouth is maybe the culprit if it because it stays alive till the bitter end so we have to kill it at this time i dont mind to have a one or two second blackscreen just before the computer is off or reboots an option could be that we load plymouth in to memory on shutdown so that there is no disk accces on shutdown just my 2ct's on this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
due the respawn of some processes i think they are (re)started again even on shutdown so they are running if the / is remounted readonly and that is why it fails i think upstart should insure that all processes are killed (also the respawning) at the moment we mount / readonly on halt or reboot my workaround(dirty hack) in the moment is adding a killall5 -9 just before line 86 of /etc/rc6/umountroot that works for me and gives no fsck's on my next (re)boots conclusion for me it's not an NM or Kernel failure its just a wrong way the shutdown procedure is handled by mixing upstart and sysv initscripts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Excerpts from Bernd's message of 2014-01-05 21:37:21 UTC: due the respawn of some processes i think they are (re)started again even on shutdown so they are running if the / is remounted readonly and that is why it fails i think upstart should insure that all processes are killed (also the respawning) at the moment we mount / readonly on halt or reboot my workaround(dirty hack) in the moment is adding a killall5 -9 just before line 86 of /etc/rc6/umountroot that works for me and gives no fsck's on my next (re)boots conclusion for me it's not an NM or Kernel failure its just a wrong way the shutdown procedure is handled by mixing upstart and sysv initscripts If you kill everything then the plymouth screen will go away, NFS rootmay fail, etc. There are other reasons it works the way it does. What is needed is a better mechanism to notify the user of what is going on and help them deal with it, and to also report those situations as bugs so we can deal with them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I have tried some workarounds from the comments and nothing seems to work. Fsck still runs at every boot. Bootchart included. ** Attachment added: Bootchart image https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3929572/+files/andrej-namizni-saucy-20131215-1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Regardless of that one comment above. But it is really frustrating if now the user's of ubuntu get blamed for not filing the correct bug. Dear folks at Canonical, you have so much information in this one thread, about how to reproduce this error. I'm not that experienced. So please, could someone reproduce this error (take a machine without any wireless capabilities) and then file the correct bug, if this bug report here is not good enough for you. It's pretty amazing that a bug that causes **filesystem errors** (if minor or not minor) does not get fixed at all and now the users get partly blamed for not filing the bug on the correct package? Hello? A default installation causes filesystem errors, reproduceable. Would someone please take those hints in this thread seriously? Like: install on a machine with a wired connection on no wireless adapters. I can reproduce this 100%. My fix is (taken from this thread): console none in /etc/init /ureadahead-other.conf OR uninstalling ureadahead at all. And more important in /etc/init/umountfs adding the following lines in the beginning of the file: service networking stop sleep 1 service networking start sleep 1 service networking stop sleep 1 killall dhclient sleep 1 That worked for me. I don't know what package to file this bug against, because it seems that it happens out of certain hardware and interaction between different packages. I'm not blaming upstart at all. I just want this CRITICAL bug to be fixed. It is around since 12.04/12.10. That's amazing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
So when I wrote 6 months ago that: If you can reproduce this issue, please file a new bug report against the sysvinit-utils package with details. It is certainly unrelated to the common issue being described here. Rather than doing this to help yourself, you switch distros, decide that upstart is to blame for a part of the system that is clearly managed by another package, and stay subscribed to the bug so that you can yell at people who are experiencing the bug that was originally reported - a bug that is unrelated to the issue that you were experiencing? This bug tracker is for helping users resolve bugs in Ubuntu. If you're not using Ubuntu, and you're not helping fix the bugs, your comments are not needed here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Excerpts from Alexander's message of 2013-10-25 05:39:16 UTC: Guys, come on! What the heck network-manager and network connections are you talking about?! This really pissed me off already! As I've said earlier, the problem is NOT in network-manager! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/comments/105 because it appears even when network-manager is not installed. I can assume (or even be sure), that network-manager HAVE some bug(s) associated with this problem, but the main cause - it's not a network-manager. And I'm sure it's in upstart. Believe me, I've spent a lot of time trying to debug this problem... You can see my comments (and debug logs) about this problem above. That was the boiling point. I've moved to Debian. Alexander I was mistaken is all. Good luck in the future, and please come back when you have helpful constructive comments. (BTW the log files that are open are being held open not by upstart directly, but by processes that are refusing to die and thus refusing to close their stdout. Upstart would be in error if it were to just close these log files while the process is still wanting to write to them.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Excerpts from Steve Dodd's message of 2013-10-21 16:16:29 UTC: That sounds plausible - I would guess wireless connections are usually torn down at the end of the user session (i.e. logout) whereas I assume wired connections persist right to system shutdown?? In theory they're brought down when network-manager is stopped. In practice they may leave lingering bits briefly after that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Guys, come on! What the heck network-manager and network connections are you talking about?! This really pissed me off already! As I've said earlier, the problem is NOT in network-manager! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/comments/105 because it appears even when network-manager is not installed. I can assume (or even be sure), that network-manager HAVE some bug(s) associated with this problem, but the main cause - it's not a network-manager. And I'm sure it's in upstart. Believe me, I've spent a lot of time trying to debug this problem... You can see my comments (and debug logs) about this problem above. That was the boiling point. I've moved to Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Sorry, forgot to added version info to #146 Ubuntu Saucy 32-bit, package version: upstart 1.10-0ubuntu7 i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I did a bit of hacking on init.d/umountroot, adding lsof and ps -ef after the remount fails. I could see that dhclient was still running, so I added before the remount: pkill -9 dhclient After this change, dhclient was gone, but the remount still failed. In lsof output I can see: init 1 root 15w REG 8,24 1134 438383 /var/log/upstart/mountall.log It seems like there is a problem in the upstart init where it is not closing files, besides the problem with dhclient. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On Wed, Oct 23, 2013 at 10:15:46PM -, Gregor Larson wrote: init 1 root 15w REG 8,24 1134 438383 /var/log/upstart/mountall.log mountall is a service that's supposed to run once at boot and then exit. If mountall is still running when you shut the system down, then you probably have a problem in your /etc/fstab (non-existent devices). We could safeguard against this by making the mountall job exit when we switch to runlevel 0 or 6. Could you please file a bug against the mountall package for this issue? It seems like there is a problem in the upstart init where it is not closing files, besides the problem with dhclient. There are many possible causes for the filesystem being held writable at shutdown; it's best to identify each of these and address them individually, rather than trying to track them all on a single metabug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
It occurs that the problem did *not* exist after a recent clean install of 13.10 (64bit Desktop CD) on a friend's notebook. While it still happens on my desktop PC. Differences: On the notebook we used wireless (b43 out of the box) internet during installation. Reboot into new system, login, shutdown is clean. On my desktop I have no wireless card at all. I use wired connection during installation. Reboot into new system, login, using system, shutdown is unclean. I haven't double-checked this though. But it maybe is a hint, that this problem occurs on machines with no wireless possibilities. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
That sounds plausible - I would guess wireless connections are usually torn down at the end of the user session (i.e. logout) whereas I assume wired connections persist right to system shutdown?? On Oct 21, 2013 3:01 PM, Christian Niemeyer chr.nieme...@gmail.com wrote: It occurs that the problem did *not* exist after a recent clean install of 13.10 (64bit Desktop CD) on a friend's notebook. While it still happens on my desktop PC. Differences: On the notebook we used wireless (b43 out of the box) internet during installation. Reboot into new system, login, shutdown is clean. On my desktop I have no wireless card at all. I use wired connection during installation. Reboot into new system, login, using system, shutdown is unclean. I haven't double-checked this though. But it maybe is a hint, that this problem occurs on machines with no wireless possibilities. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I'm seeing this in 13.10 as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Yeah, still exists in 13.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
This still happens in 13.10 (saucy). This time I installed the Beta-2 of Lubuntu (thus using an lxsession). Reboot or shutdown fails everytime. It hangs for around ten seconds, then it reboots and fsck shows deleted orphaned inode. Only helps to uninstall network-manager-*, nm-*, modemmanager, ureadahead. How come this hasn't been fixed yet? It is reproduceable all the time for me. (My router is fine and network also. I had problems with my old router and dnsmasq in 12.04 but no unclean shutdowns.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I have the same problem on 13.04, which is solved by 2 steps (as mentioned above): 1) uninstalling ureadahead or adding console none to /etc/init/ureadahead-other.conf 2) killing dhclient in umountfs. Indeed, why it has not been fixed for years -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Dmitry, I confirm your solution. I already uninstalled ureadahead (no need for it with a SSD). I added killall dhclient to my /etc/init.d/umountfs (at the beginning of the do_stop function). This problem happens for me only when I use the regular wired ethernet on my ThinkPad X230 (not just when the laptop is docked to the UltraBase as I've reported earlier) . It doesn't happen when I'm using wireless. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I've tried patches in mentioned in comment #137, but they didn't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
My problems (on current saucy) were caused by bugs in upstart (affecting ureadahead) and network-manager. The patches in bug #1181789 and bug #1169614 give me a clean unmount and shutdown. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
In my case the bug with unclean shutdown happens only when my machine (Thinkpad X230) is docked to the Thinkpad ultrabase when shutting it down. When I shutdown outside of a dock, everything is fine. I don't use ureadahead (have SSD), doesn't matter if there are mounted network filesystems or not, if NetworkManager is running or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Finally did a workaround of this bug with: 1) killing dhclient on umountfs step 2) /etc/init/ureadahead-other.override with manual start AFAIK this bug exists since 12.10 and I have no idea why it still doesn't fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
This does seem like a bug in upstart. It seems to me that there needs to be a command to say upstart, close all of your log files and do not reopen them so that one can remount / readonly. Systems may have things that want to keep running right up until poweroff/reboot, but that make use of 'console log'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I added the following line to /etc/init/ureadahead-other.conf to disable logging for this particular Upstart job: console none This prevents the log file from keeping the file system busy. The only downside is that anything logged by ureadahead-other goes to /dev/null instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
P.S. You will have to reboot 2 times after adding console none for it to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
The cause of ureadahead issue is upstart. The pure case unrelated to ureadahead is Bug lp: #1181789. In some cases upstart might hold log files opened for writing for other daemons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Bug #1181528 for ureadahead/upstart issue. Unfortunately the conditions to reproduce are not clear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On Thu, May 16, 2013 at 04:21:12PM -, Max wrote: 'ps uw' only shows processes belonging to the current user. Unless PID is specified Oops, true. So the process is definitely not running. Also, please file a bug report against the ureadahead package for this package, and post the number of the new bug here. I would rather file a bug against upstart. As the developer, I am asking you to file a bug against ureadahead. Ureadahead does his job and exits with status 4 or 5 depending either absent pack file or mainline kernel is running. Init on the other hand does not close the log file for some reason. Because ureadahead is not behaving correctly under upstart, and somehow manages to cause upstart to not notice that the process has exited. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
'ps uw' only shows processes belonging to the current user. Unless PID is specified Also, please file a bug report against the ureadahead package for this package, and post the number of the new bug here. I would rather file a bug against upstart. Ureadahead does his job and exits with status 4 or 5 depending either absent pack file or mainline kernel is running. Init on the other hand does not close the log file for some reason. There is a chance however that this variant of bug might be triggered by more than one mount in addition to root filesystem. /etc/init/ureadahead-other.conf does not contain instances. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
There is at least one more cause of busy / besides network-manager in Raring 13.10. I have noticed file /var/log/upstart/ureadahead-other.log opened for writing by init when /etc/init.d/umountroot was running. It seems that the problem was caused by absent pack file in /var/lib/ureadahead/ for a partition added some time after installation. I can not find config responsible for presence of /sys/kernel/debug/tracing/events/fs required for ureadahead. I am in doubt if stop on condition is intentionally missed in /etc/init/ureadahead-other.conf I do not like ureadahead-other status # initctl status ureadahead-other ureadahead-other start/running, process 811 # ps uw 811 USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND (no process 811) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Hi Max, On Tue, May 14, 2013 at 04:17:18PM -, Max wrote: There is at least one more cause of busy / besides network-manager in Raring 13.10. I have noticed file /var/log/upstart/ureadahead-other.log opened for writing by init when /etc/init.d/umountroot was running. It seems that the problem was caused by absent pack file in /var/lib/ureadahead/ for a partition added some time after installation. I can not find config responsible for presence of /sys/kernel/debug/tracing/events/fs required for ureadahead. I am in doubt if stop on condition is intentionally missed in /etc/init/ureadahead-other.conf I do not like ureadahead-other status # initctl status ureadahead-other ureadahead-other start/running, process 811 # ps uw 811 USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND (no process 811) 'ps uw' only shows processes belonging to the current user. Please check 'ps auwx'. Also, please file a bug report against the ureadahead package for this package, and post the number of the new bug here. When filing that new bug, please attach the contents of /var/log/upstart/ureadahead-other.log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
** Tags removed: kernel-da-key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Except for dependency upon Nvidia drivers, I would be quite satisfied with 12,04. I really would like to put Nvidia drivers in the trash where they belong. The list of 13.xx BUGs preventing the switch from 12.04 is getting shorter. Please shorten the list by fixing this BUG promptly. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
See also LP: #869635. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Paul, In Quantal 12.10 it is the bug lp: #1124803 NetworkManager doesn't respond to SIGTERM in daemon mode. And that patch fixes the issue for network-manager 0.9.6 (however there are no .deb packages). In 13.04 Raring, network-manager maintainers in Ubuntu missed that upstream dropped distro-specific defines, so network-manager-0.9.8 packages is affected by the bug lp: #1169614 dhclient is not stopped during shutdown. These two bugs lead to the same result during shutdown: mount: / is busy That is actually hidden from the users by the plymouth splash screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I'm experiencing similar issues on an EXT-3 filesystem. There are no inode/block errors reported by fsck but the root filesystem (/ is mounted on /dev/sda2 in my case) fails the fsck check at boot. % dmesg | grep sda2 EXT3-fs (sda2): recovery required on readonly filesystem EXT3-fs (sda2): write access will be enabled during recovery EXT3-fs (sda2): recovery complete EXT3-fs (sda2): mounted filesystem with ordered data mode [Edited for brevity] This happens on every boot. The other partitions (and there are 6 including swap) all pass the fsck check. The workaround of deselecting Available to all users in Network Connections discussed above works for me. Seems reasonable to assume that this is not filesystem specific and that the shutdown is not clean for some reason. Quantal 12.10 Linux 3.5.0-28-generic #48-Ubuntu SMP Tue Apr 23 23:05:48 UTC 2013 athlon i686 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Max, I did a quick search for the NetworkManger source code. Many variations and levels of development exist. Since I have no experience as a developer or QA type in the Ubuntu arena and have repeatedly submitted DETAILED steps for this 100% reproducible problem, I will pass on trying to fix it myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
1. Will I have to download and install a compiler and a linker? Sure: sudo apt-get install build-essential 2. Will I have to recompile the kernel to use the updated NetworkManager? No, just network-manager: sudo apt-get build-dep network-manager apt-get source network-manager cd network-manager-0.9.8.0 First of all I would suggest you to check that original package can be build without any errors. For dpkg-buildpackage I had to disable test (debian/rules file, --enable-tests=no instead of --with-tests in ./configure invocation) fakeroot dpkg-buildpackage -b -uc Successful build will finish with .deb files created in the parent directory.. Edit .c files as described in Comment 114. It is better to edit debian/changelog file as well and add an additional entry to the top of the file with another version suffix. This step will allow to avoid confusion which package is installed. Again fakeroot dpkg-buildpackage -b -uc (option -nc can be added to compile only updated files) You should have new .deb file that can be installed with sudo dpkg -i ../exact name of network-manager_0.9.8*.deb The details can be found in http://www.debian.org/doc/manuals/maint-guide/build.en.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Is this bug still present in the released 13.04 version? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
ABSOLUTELY! 64-bit Desktop 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 IF Internet connection to the modem exists and Ethernet connection from my desktop to the modem and Enable Networking checked and Shutdown or Restart or Reboot THEN Bad shutdown fsck from another copy of Ubuntu will indicate problems, see attachment END Dropping the Ethernet connection by unplugging the Ethernet cable or unchecking Enable Networking before a shutdown or reboot will ALWAYS keep the problem from occurring. This problem has existed since 12.10 and has been discussed but not fixed. If it is helpful to know, while the Ethernet connection is up small keepalive packets seem to be sent and received from time to time. ** Attachment added: Dirty fsck from BAD network enabled restart_2013-04-26 18:45:45.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3655573/+files/Dirty%20fsck%20from%20BAD%20network%20enabled%20restart_2013-04-26%2018%3A45%3A45.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Ernie, have you tried the suggestion from the comment #114? (Bug lp: #1169614) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Hi Max, The last time I touched a compiler was in the windoze world about ten years ago. 1. Will I have to download and install a compiler and a linker? 2. Will I have to recompile the kernel to use the updated NetworkManager? Advise please. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Morning, 'halt'... and / is busy again. VERBOSE=yes in /etc/default/rcS didn't help either. Just a few messages are added: * Will now unmount temporary filesystems tmpfs has been unmounted * Will now deactivate swap swapoff on /dev/sdb1 * Mounting root filesystem read-only... umount: /run/lock: not mounted umount: /run/shm: not mounted mount: / is busy I don't know how to debug it even more. Any ideas? P.S.: with 3.8 kernel from PPA Xorg doesn't start (lack of KMS or something). So currently I can't fully test it with a new kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Russel, please read my comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/comments/105 carefully. I repeat: I have neither plymouth nor network-manager nor modemmanager nor wicd installed. Just plain /etc/network/interfaces. +guessnet. /etc/network/interfaces is the native way to configure network in Linux distributions. Why should I use something else, when 'interfaces' covers 100% of my needs? Disabling network in NM/replacing NM just hides the real bug. Problem is NOT in network manager. It is somewhere deeper (like Steve supposed, a kernel bug, or a bug in sysvinit-utils). Today's morning I've got that 'busy' with halt: acpid: exiting speech-dispatcher disabled; edit /etc/default/speech-dispatcher * Stopping VirtualBox kernel modules Stopping UPS power management: apcupsd exiting, signal 15 apcupsd[1444]: apcupsd shutdown succeeded apcupsd. * Asking all remaining processes to terminate... * All processes ended within 2 seconds [54994.264815] init: Disconnected from system bus [54994.484761] tg3 :10:00.0: wake-up capability enabled by ACPI * Unmounting temporary filesystems... * Deactivating swap... umount: /run/lock: not mounted umount: /run/shm: not mounted mount: / is busy * Will now halt [54995.304424] kvm: exiting hardware [54995.305569] sd 0:0:0:0: [sda] [54995.305929] sd 0:0:0:0: [sda] [54995.958554] System halted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Steve, thanks for the info. As I've mentioned earlier, I'm using autofs. I think that such names like 'tmp/autoX' are autofs temporary mount points. Also I have /tmp mounted as tmpfs. So my guess is that tmpfs is getting unmounted BEFORE autofs daemon have been terminated (unmounted it's mountpoints). So that autofs mount points can't be unmounted (because they were left on old /tmp with tmpfs). Now starting and stopping of services in Ubuntu not always works as it is expected. Earlier when services got started from /etc/init.d it was slow but predictable. Services have been launched one by one. What is really going on now?.. Looks like no one really knows. Sometimes it looks like that all this stuff is launched asynchronously (simultaneously) and in background. Some kind of unpredictable hell, full of 'race conditions'. And if you don't see it that doesn't mean that this is not exist. For me it's like playing with fire. Today you have won... But tomorrow you can burn. For an example, I've seen a lot of times, when I do 'restart service_name' command I'm getting almost immediately output to console that service have been restarted. But meanwhile, when I've tried to connect to that service it wasn't ready! It is still being launched/restarted! So why do I get output to the console, that the service have been restarted when in fact it still DOESN'T? I'm just suspecting that the problem with 'busy' can be even deeper than I thought... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Ernie, please, try to rebuild network-manager with #define TARGET_DEBIAN added to src/dns-manager/nm-dns-dnsmasq.c src/nm-device.c src/nm-manager.c in the very beginning of that files. Perhaps you might need to change the line 45 of debian/rules from --with-tests to --enable-tests=no -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Something really going wrong here. Today's morning I've found reaaally something new! I'm seeing this for the first time ever. I've tried to halt the system (not poweroff as usually): * Unmounting temporary filesystems... umount: /tmp/auto6FJPRq (deleted): not found umount: /tmp: device busy. ... EXT4-fs (sdb2): re-mount. Opts: (null) ... System halted. What's wrong with /tmp now?! Arrrgh! All these Ubuntu bugs are beginning to drive me insane. My own conclusion: init/upstart is totally screwed up! Filesystem corruption is unacceptable! For _ANY_ operating system! Ubuntu? On desktop? In production?! Are you kidding me?! Of course, no! Never!! It's sad, but Ubuntu is suitable only for 'eye-candies' (свистоперделки in russian). No more. Not for work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Alexander, get rid of NM and install wicd to learn if the problem(s) still persist. Using wicd, I get clean and fast shutdown in 5 seconds, with no fsck checks on reboot. Worth a try! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On Tue, Apr 16, 2013 at 08:38:29PM -, Alexander wrote: Something really going wrong here. Today's morning I've found reaaally something new! I'm seeing this for the first time ever. I've tried to halt the system (not poweroff as usually): * Unmounting temporary filesystems... umount: /tmp/auto6FJPRq (deleted): not found umount: /tmp: device busy. ... EXT4-fs (sdb2): re-mount. Opts: (null) ... System halted. What's wrong with /tmp now?! That's a very good question. But it has nothing to do with upstart; for some reason, /proc/mounts on your system reports a tmpfs mounted at /tmp/auto6FJPRq (deleted), which it can't unmount, and as a result /tmp can also not be unmounted cleanly. What's unusual is that something on your system was able to delete the mount point of an active mount. This shouldn't happen at all. So you may be looking at a kernel bug, or a bug in sysvinit-utils (which handles the unmounting at shutdown). If you can reproduce this issue, please file a new bug report against the sysvinit-utils package with details. It is certainly unrelated to the common issue being described here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Russel, When using the CLI, I got an error and could not install wicd on 13.04 However, I was able to install it via the software center. Each time that I attempted to use it, a connection failure message occurred immediately after the requested password was entered. Are you able to install/execute wicd using 13.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Another data set: 1. ATT is my ISP. My Desktop connects to a DSL modem via Ethernet. 2. There seems to be some keepalive traffic. A packet of 64 or 121 bytes gets sent or received about every 10 seconds. This activity appears to happen in 12.04 which functions correctly and in 13.04 which fails 100% of the time. 3. Shutting down in this state (Enable Networking checked but NO explicit Internet activity) will result in an error every time. 4. The connection will drop if I unplug the Ethernet cable. In that state I can reboot with NO errors. Since I can manually force the connection to drop by either unplugging the Ethernet cable or unchecking Enable Networking, shouldn't the network manager also drop the Ethernet connection when a restart/reboot/shutdown is requested? I pose the question because the failure will never occur if the network connection has been dropped. Perhaps the keepalive traffic is not being forcibly killed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Ernie, I'm still on 12.10 (I'm waiting for RC before upgrading) and using wicd with a wireless connection, so I'm not sure why you are getting an error with your ethernet connection. You have probably explored all the options... In the next couple of days I'll upgrade one computer to 13.04RC and report back if wicd can be successfully installed or not. (It is obviously in the 13.04 repos if you got it though Software centre.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
1) Problem appears on different hardware. I mean totally different (except for my usb hdd, from which the system boots). 2) I run memtest about a year ago... But I don't see any oops-es, hangs or kernel panics. So the problem is not related with (broken) hardware. 3) How I've removed plymouth? I read about plymouth in comments to #556372. People suggest to install plymouth-dummy package (which has no mountall dependency) so after that plymouth can be easily removed. I have neither plymouth nor network-manager nor modemmanager nor wicd installed. Just plain /etc/network/inerfaces. +guessnet. 4) I'm bringing network interface up manually from /etc/rc.local. Because 'ifup -a' called from init-scrips doesn't work correctly (bug). 5) The harder I'm trying to debug this bug, the less it appears (he knows that I'm hunting on him! haha). 6) I can speak russian, если что. 7) currently I can't set HALT=halt in /etc/default/halt. Because most of the time shutdown is scheduled and done automatically (and I can be far away from computer at that moment). But I'll do that soon. 8) Problem doesn't appear 100% of the time (at least for me). And also not related with any of my debug scripts. 9) Both root and swap partitions are on my usb harddrive. So, maybe it's somehow related to usb? Or swap? I don't know is it important... but root and swap are mounted from fstab by label: LABEL=root / ext4errors=remount-ro 0 1 LABEL=swap noneswapsw 0 0 10) I'm also using autofs daemon. Maybe it's somehow related to it? 11) Now I've removed all my debug parts from umountroot. And added two scripts: /etc/rc0.d/S59-before-umountroot: #!/bin/bash /sbin/sysctl kernel.printk=7 4 1 7 /bin/dmesg /upstart-messages-1-before-ro-`date +%s`.log /etc/rc0.d/S75-before-halt: #!/bin/bash /bin/dmesg /upstart-messages-2-after-ro-`date +%s`.log (also added symlinks to rc6.d) But, I've got nothing interesting: ... [22482.298335] init: smbd main process (1057) killed by TERM signal [22482.299101] init: tty4 main process (1246) killed by TERM signal [22482.299659] init: tty5 main process (1255) killed by TERM signal [22482.300259] init: tty2 main process (1293) killed by TERM signal [22482.304610] init: tty3 main process (1294) killed by TERM signal [22482.305310] init: tty6 main process (1299) killed by TERM signal [22482.315235] init: irqbalance main process (1327) killed by TERM signal [22482.315828] init: cron main process (1339) killed by TERM signal [22482.318599] init: tty1 main process (2165) killed by TERM signal [22484.047088] init: Disconnected from system bus [22484.190023] tg3 :10:00.0: wake-up capability enabled by ACPI Both logs are the same. 12) cat /proc/cmdline root=LABEL=root ro ipv6.disable=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 I just want to say about my expirience here. Maybe it adds some useful details to understanding what's going on. Ubuntu = 12.04 amd64 kernel = 3.5.0-22-generic. rootfs = btrfs Sometimes I was able to see that / is busy before halt. Especially when my torrent client is seeding/leeching much torrents from/to another partition on another USB drive, and before shutdown I don't stop torrents. Because I have no time to debug this issue. I just installed kernel from http://pf.natalenko.name/ with BFS shedulers from Con Kolivas. And bug disappears like a charm. So. My point is: This issue is more like kernel issue, not init scripts. And maybe it is related to old good https://bugzilla.kernel.org/show_bug.cgi?id=12309 I don't know, maybe I'm wrong. ** Bug watch added: Linux Kernel Bug Tracker #12309 http://bugzilla.kernel.org/show_bug.cgi?id=12309 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 Forget to say. I have plymouth installed, but just removed of quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
** This bug is no longer a duplicate of bug 1124803 NetworkManager doesn't respond to SIGTERM in daemon mode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I have broken the link to duplication of bug #1124803 NetworkManager doesn't respond to SIGTERM in daemon mode. This bug have been reported by Ernie and in the discussion of bug #1124803 he insists that his bug has not fixed. Network manager 0.9.6.0 in 12.10 quantal is really affected by that bug, and if the patch mentioned there is applied system shuts down correctly. On 'stop network-manager' dhclient is stopped as well. If network-manager 0.9.8.0 from Raring is installed to 12.10 Quantal then dhclient for some reason (unclear for me) does not open lease file in /var/lib/NetworkManager so root filesystem can be cleanly remounted readonly. In Raring network-manager 0.9.8.0 opens a lease file in /var/lib/NetworkManager, but after 'stop network-manager' dhclient (intentionally?) remains alive. The PID of dhclient is mentioned in /run/sendsigs.omit.d/ so, if I guess correctly, dhclient is not stopped during shutdown and /etc/init.d/umountroot can not remount / readonly due to the lease file open for writing. Any volunteers to debug further? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I have Network manager installed in Ubuntu 12.04, but I have / busy only with generic kernel. With pf-kernel I have clear shutdown. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
In another perhaps related bug 1124803, it was suggested to try wicd. Unfortunately wicd would not install on 13.04 amd64.deb for me. Failure indicated partway through the installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 Alexander, by the way, how have you managed to remove plymouth? mountall depends on plymouth, initscripts depends on plymouth. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 It turned out to a kind of mystery. No files are left open for writing but device is busy and can not be cleanly remounted readonly. Moreover it is not clear how to reproduce the issue. Concerning the formalities, since the issue addressed in the last comments have nothing with bug lp: #1124803 NetworkManager doesn't respond to SIGTERM in daemon mode, the link to that bug might be removed. On the other hand original description of this bug fitted quite well to bug lp: #1124803 and it has nothing common with removing of network-manager, plymouth, etc. In my opinion the case with no bunch of packages should be filed as a dedicated bug with clear statements concerning conditions and ruled out hypotheses. Alexander, actually I can not figure out which way debug scripts can block umount, but since they provide no useful info, it is interesting what would happen if you completely remove debug scripts and temporally set HALT=halt in /etc/default/halt to have time to inspect last messages without writing them to a file. Have you tried memtest on that box? Have you experienced kernel panic or Oops due to kernel modules or hangs due to e.g. graphics card driver? Concerning the bug lp: #1124803, there are tails of modem-manager and so network-manager again. I can not comment on plymouth hangs since removing of quiet and splash from GRUB_CMDLINE_LINUX_DEFAULT works like a charm for me. (Actually I have tried an upstart task with /bin/plymouth hide-splash command before.) To obtain more debug info I would suggest to run sudo initctl log-priority info before shutdown (perhaps 'sudo sysctl kernel.printk=7 4 1 7' to see the messages on the screen as well) and add dmesg /upstart-messages.log to /etc/init.d/umountroot There is an issue with network manager proliferated to plenty of bugs, but it can be easily fixed. The problem with busy / when no processes are left and no files are open is very strange. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 The original description does not mention removing of network-manager and other packages. The phrase concerning redundant open files in unclear for me. Is there any files open for writing? I wonder if the problem if the debug scripts is removed. Instead of plymouth removing, the splash screen can be suppressed by setting empty GRUB_CMDLINE_LINUX_DEFAULT= in /etc/default/grub (remove default options quiet and splash) and run sudo update-grub /etc/default/halt can be temporally changed to HALT=halt this will allow to inspect very last messages during shutdown. VERBOSE=yes in /etc/default/rcS will add a couple more messages. Finally sudo initctl log-priority info sudo sysctl kernel.printk=7 4 1 7 before shutdown makes upstart quite verbose. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
Max, as I've understood, no splash doesn't disable plymouth. Some people
suppose that the freezed plymouth is the cause:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1019347
I've decided to find it out and totally purged plymouth from system. But that
didn't help.
So, what do we have now?
I've modified /etc/init.d/umountroot script (part at 86 line):
=
for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
do
mount$MOUNT_FORCE_OPT -n -o remount,ro -t dummytype
dummydev / 2/dev/null \
|| mount $MOUNT_FORCE_OPT -n -o remount,ro
dummydev / 2/dev/null \
|| mount $MOUNT_FORCE_OPT -n -o remount,ro
/
ES=$?
# [ $VERBOSE = no ] || log_action_end_msg $ES
log_action_end_msg $ES
if [ $ES -gt 0 ]
then
LOG=/mega-log-`date +%s`
echo `date`: Attempt ${i}: remount rootfs failed! Trying
again... #| tee -a $LOG
echo `date`: Attempt ${i}: remount rootfs failed! Trying
again... $LOG
#sleep 1
{ cat /proc/mounts ; echo ; ps aux ; echo ; /usr/bin/lsof
; echo ; } $LOG
/bin/fuser -v -m -u / 1/dev/null 2 $LOG
sleep 1
else
break
fi
done
=
Today's morning I've got a 21 message / is busy at shutdown.
Early, I thought that the cause is that some processes are accessing the disk
during shutdown (writing). Some processes which are not terminated on time, so
/ is busy message appears.
Now I'm looking into logs and... Well, looks like it isn't the real cause.
I don't see any files opened for writing (except pipe, @/com/ubuntu/upstart,
/dev/null and /dev/console).
So, more and more I think, that this bug is in 'init/upstart'... or in kernel!
It's not so easy to reproduce it. I've tried a lot of times to reboot machine
under heavy cpu and I/O load and bug doesn't apper (a lot of times in about
10-15 minutes).
But bug appears more frequently when uptime is high enough (at least 1/2 of a
day).
Steps to reproduce: push power button from running X session.
One more interesting thing: my root partition is on usb hard drive.
If I'll have some more free time near future, I'll try to test it with a
new kernel ( 3.5).
** Attachment added: mega-log-1365656098
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3640749/+files/mega-log-1365656098
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 ** Attachment added: S59-2013-04-11.log.old https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3640750/+files/S59-2013-04-11.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 ** Attachment added: S75-2013-04-11.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3640751/+files/S75-2013-04-11.log ** Attachment removed: S59-2013-04-11.log.old https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3640750/+files/S59-2013-04-11.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 ** Attachment added: S59-2013-04-11.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3640770/+files/S59-2013-04-11.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 I have exactly the same problem. Everything stopped, dhclient, network manager and plymouthd as well, no redundant open files, everything what should be umounted is umounted. But every reboot I still see umount: / is busy and then fsck at start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 ***
https://bugs.launchpad.net/bugs/1124803
As I've understood, unmount of tmpfs filesystems is called from
/etc/rc{0,6}.d/S40umountfs right?
My /etc/rc{0,6}.d/S59 script calls 'cat /proc/mounts S59.log'
Then, why do I see tmpfs in log?
$ grep tmpfs S59.log
udev /dev devtmpfs rw,relatime,size=1273868k,nr_inodes=318467,mode=755 0 0
tmpfs /run tmpfs rw,nosuid,relatime,size=513264k,mode=755 0 0
none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0
none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 Forgot to mention that the lsof launched from S59 didn't show any files opened for writing too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 Steve Langasek, maybe it's a race condition. When init scripts trying to unmount root, they fail because of opened files. But, when I check for opened files in S75 script those processes had been terminated already. So, we see no open files. I'll try to catch it with S59 script (before S60umountroot). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 Marius B. Kotsbak, no, currently, I can't, sorry. (lack of time) Upd: I also have tmpfs /tmptmpfs defaults string in /etc/fstab. Maybe this is the case... I'll check this too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 I think, the problem is somewhere deeper... In upstart/init. I've purged network-manager, modem-manager and even plymouth! And added S75 script in /etc/rc0.d: cat /proc/mounts /usr/bin/lsof /bin/fuser -v -m -u / 1/dev/null But as you can see, the problem remained. kernel 3.5.0-22-generic, quantal. ** Attachment added: mount-lsof-fuser https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3617358/+files/mount-lsof-fuser -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 Alexander, could you test it using a Raring daily image? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 Alexander, your lsof output doesn't show any files open for writing on the root filesystem except for the S75 script's own log. If you're getting ext4 corruption on shutdown, that seems to be unrelated to this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 Using 64-bit 3.8.0-16-generic #26-Ubuntu SMP Mon Apr 1 19:52:57 UTC 2013 from the 2013-04_02 daily build: 1. NetworkManager stopped correctly (immediately) via sudo stop network-manager. 2. A reboot to an alternate system and fsck of the system under test presented errors. Regardless of whether I stopped or restarted NetworkManager, as long as I manually unchecked Enable Networking, a clean shutdown would occur and a subsequent fsck would show no errors. A process (maybe more than one) is being gracefully shut down when I manually uncheck Enable Networking but is not getting properly shutdown via sudo stop network-manager. Hope this data point is helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
*** This bug is a duplicate of bug 1124803 *** https://bugs.launchpad.net/bugs/1124803 From the upstream report [1], the fix is for Ubuntu to carry the patch against NetworkManager [2]. Since this is correctly understood and addressed in bug 1124803 as Max points out, this is a duplicate bug report, so I'll mark it so. [1] https://bugzilla.gnome.org/show_bug.cgi?id=683932 [2] https://bug683932.bugzilla-attachments.gnome.org/attachment.cgi?id=224204 ** Bug watch added: GNOME Bug Tracker #683932 https://bugzilla.gnome.org/show_bug.cgi?id=683932 ** This bug has been marked a duplicate of bug 1124803 NetworkManager doesn't respond to SIGTERM in daemon mode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
It seems that the issue may be connected with bug 1124803 NetworkManager doesn't respond to SIGTERM in daemon mode That patch helped me on 12.10. But I am puzzled by the reports that this bug has not fixed in Raring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Does anybody know if the workarounds posted here remain effective after a kernel upgrade to 3.5.0-26? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Franciso, I am using 3.5.0-26, and the my comment at #75 holds true. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Do not be deceived. This is a 1210 and 13.04 problem. 64-bit 1204 3.2.0-39-generic #62-Ubuntu SMP Thu Feb 28 00:28:53 UTC 2013 and prior 12.04 64-bit versions work just fine! It would be quite delightful if someone would correct this problem of failing to shutdown properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I repeat. This is a 12.10 and 13.04 problem. 64-bit 1204 3.5.0-26-generic #42~precise1-Ubuntu SMP Mon Mar 11 22:17:58 UTC 2013 and prior 12.04 64-bit versions work just fine! A fix for this problem of failing to shutdown properly would be much appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Thanks again Russell. I'm upgrading to 3.5.0-26. It's good to know that the upgrade won't break the workarounds. And of course I agree with Ernest that a proper fix for this bug would be very much appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Does anybody know if the workarounds at #10 and #13 (or the suggestion at #57 and #61, or the one at #60) remain effective after a kernel upgrade to 3.5.0-25? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
