[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Not directly, but I would assume so, as unchecking 'Available to all users' still works with 3.5.0-25. I have also tried your suggestion at #60, thanks. It works for me -- but I have reverted to the simple 'uncheck' as there seems no downside in my installations and any future fix should be with NM not the init system. -- 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 Russel. I will 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
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Well, network usually does not break by killing dhclient, at least not if the lease does not expire just in this second. If we ignore this race, probably only modem processes are left. But these are not even considered by the add_sendsigs_omissions.patch. The patch only touches nm-dhcp-dhclient.c, nm-dhcp-dhcpcd.c, nm-dns-bind.c and nm-dns-dnsmasq.c. Except for the lease/shutdown race none of these should be required for anything that is already mounted - the kernel nfs client already knows the IP of the server. If we don't want to ignore the lease race and we don't trust NM to kill sub-processes we need a to run killall5 a 2nd time and this time it only must ignore fuse processes. However, if the root file system or /etc or /var are on NFS, we cannot fix this race at all and have to leave it to the admin to provide sufficiently long leases. -- 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 Mon, Feb 18, 2013 at 08:32:14AM -, Bernd Schubert wrote: Well, network usually does not break by killing dhclient, Irrelevant. The dhclient process is managed by NM, and sendsigs must not interfere with it. If we don't want to ignore the lease race and we don't trust NM to kill sub-processes We *require* NM to clean up its subprocesses. This is the only sane architecture. If NM is not doing so, that's a bug in NM. we need a to run killall5 a 2nd time 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
Re: [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
On 02/18/2013 10:10 AM, Steve Langasek wrote: On Mon, Feb 18, 2013 at 08:32:14AM -, Bernd Schubert wrote: Well, network usually does not break by killing dhclient, Irrelevant. The dhclient process is managed by NM, and sendsigs must not interfere with it. If we don't want to ignore the lease race and we don't trust NM to kill sub-processes We *require* NM to clean up its subprocesses. This is the only sane architecture. If NM is not doing so, that's a bug in NM. Well, do as you like, but from my point of view an init system that does not properly kill processes is broken by design. Relying on something is always wrong, especially if it is system critical (I got severe data loss on my btrfs partition due to this bug here). killall5 is there to enfore things, not to rely on them... It is nice that it speeds up shutdown, but that is only a side effect. So far I also only see a patch in NM that made it worse than it had been before. Properly fixing NM is certainly correct, but that still is no enforcement that shutdown properly works. I know how to fix it on my systems and I'm going to publish that information, but other than that I'm giving up on upstream. -- 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 fail to understand why so many people are insisting this is a kernel bug. It isn't. What basically happens is that the network-manager process is not killed by killall5. This process also has an open file descriptor and therefore the root partitions cannot be mounted read-only before shutdown, as the kernel reports it is busy. Network-manager will not be killed due to the ubuntu patch add_sendsigs_omissions.patch, which was added to NM for a similar reason: From: Mathieu Trudel-Lapierre mathieu.trudel-lapie...@canonical.com Subject: Move NM's spawns pid files to /run/sendsigs.omit.d. Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/869635 The pidfiles are only used by NM to start and be able to stop the same process, their actual location doesn't overly matter. In this case, putting them under /run/sendsigs.omit.d allows shutdown to skip over those as handled by an upstart job, and in fact they are (although indirectly). I have no idea what Mathieu actually intended with this patch, but it is entirely wrong and made everything worse. Instead of refusing to kill NM, it needs to be killed, which is just the other way around than what the patch is doing. The only way to fix this from kernel point of view would be to write a kernel patch to allow to mount read-only while there are still file descriptors, which have write access. All those FDs would need to be closed from the kernel side and propably would cause application crashes. -- 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 Sun, Feb 17, 2013 at 09:04:32PM -, Bernd Schubert wrote: I have no idea what Mathieu actually intended with this patch, but it is entirely wrong and made everything worse. Instead of refusing to kill NM, it needs to be killed, which is just the other way around than what the patch is doing. The intent, which is correct, is that NM itself shuts down these subordinate processes as part of the network shutdown *after* /etc/init.d/sendsigs is run, instead of having them killed in an uncontrolled manner by /etc/init.d/sendsigs and breaking the network. Perhaps NM is failing to shut down the processes; but the sendsigs handling itself remains correct. /etc/init.d/sendsigs should not be allowed to indiscriminately terminate processes that are needed for the network to run; these processes need to be ended later, after /etc/init.d/umountnfs.sh has unmounted all network filesystems. -- 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 also occurs in 64 bit 1304 (Raring) with kernel 3.8.0-6-generic. Tested Friday 2013-02_16 -- 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 just tested newly released kernel 3.5.0-24. It also works with uncheck 'Available to all users' workaround mentioned above. -- 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
Yes, you are right, Francisco, I didn't uncheck the all users option. I am glad it helped. I hope others with this problem will also find this page and solve this problem this way. I don't know if an update to the kernel or any part of the system config will break this. Previously I had root filesystem problems, that was fixed by some killall commands ( I don't remeber the site, that suggested it) and I thought the problem is gone, but a few days later it started to do home corruptions, so I searched for this symptom again, and found this bug. Since Linux has a command for everything, I thought there must be one for disabling network through Networkmanager. I like Networkmanager, so I didn't want to disable it (I travel with my laptop and use wireless connection, so this is convenient.), but this command is perfectly does its job. -- 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 Francisco, I created a script in /etc/init.d (I copied from an existing script actually), at the stop part I inserted the command nmcli nm enable false and at the start part true. Then I created a symlink for it S60networkm in /etc/rc2...rc5.d, and also K05networkm in /etc/rc0.d and rc6.d. -- 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 Sandor. I did something similar, but in /etc/init. (See #60.) Your comment (at #57) was very 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
Hi Fransisco' I agree that latest kernel has improved the situation. It is now possible to simple uncheck 'Available to all users' in NM to get a clean shutdown. Beware if you create a new network connection, because it defaults to 'Available to all users' checked. Before the latest kernel, this solution wouldn't work for me. -- 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
For people who need to live with this bug, it might be good to stress that Sandor' s suggestion (#57 and #61) and my little hack (#60) rely on the workaround at #13, which is effective with kernel 3.5.0-23-generic (the current kernel in Ubuntu 12.10), but not with kernel 3.5.0-22-generic (the previous kernel in Ubuntu 12.10). I believe (but am not quite sure) that the workaround was also ineffective with kernel 3.5.0-21-generic and that it was effective with the previous Quantal kernels. While this bug is not fixed I will think twice before doing a kernel upgrade on Quantal, as a disk check on every boot makes the system nearly unusable to me. I am not blaming the kernel, but it appears that the workaround depends upon the timing of an upstart race condition, which may change with the kernel version. When a new kernel version comes out, I would like to know if the new kernel will not break the workaround again. -- 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 Russel, With Sandor's hack (see #57 and #61, or, alternatively, #60) you do not even need to uncheck Available to all users, as the shutdown and startup scripts take care of disabling and enabling the NM. -- 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 all, I don't know how much time it may take to find why Networkmanager doesn't handle open files properly at shutdown, but since my home was also failing every time and manual disable networking through NM solved my problem (and shutdown is much faster), I added nmcli nm enable false|true to my stop and start-up scripts. I wrote this to help others who may also have this problem and don't want to manually disable / enable networking everytime. -- 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 Sandor, Where exactly did you add the calls to nmcli? -- 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 also occurs in 64 bit 1304 (Raring) with kernel 3.8.0-3-generic. Tested Friday 2013-02_01 -- 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
Today I' ve seen an improvement in Quantal: the workaround suggested at #13 resumed working after I got a kernel update from 3.5.0-22-generic to 3.5.0-23-generic. Per Sandor' s suggestion, I have added to /etc/init two files that relieve me from the burden of manually disabling/enabling the network manager. These two files are shown below. $ cat /etc/init/hack1-for-nm-bug.conf description Hack 1 to circumvent NetworkManager bug in Ubuntu 12.10 start on started gdm script /usr/bin/nmcli nm enable true end script $ cat /etc/init/hack2-for-nm-bug.conf description Hack 2 to circumvent NetworkManager bug in Ubuntu 12.10 start on runlevel [016] script /usr/bin/nmcli nm enable false end script -- 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
Ok, where to next? Is more information needed from users? It's gone quiet on what seems like an identified problem and narrowing evidence pointing to two culprits. -- 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
Russell, the problem in network manager needs to be debugged. No milestone is set yet, so its not known when it will be resolved, but it does seem likely that the problem will be easy to fix given how reproducible it is and how much insight we have into it now. -- 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
Stupid question, why should network-manager not be killable? From my point of view everything should be killed before a shutdown except of processes, which are absolutely required to continue the shutdown/reboot. So for example if you are using unionfs-fuse for /, /etc or /var and kill its daemon, shutdown cannot continue. But how is that related to the network manager? Assuming there is a network file system involved, kill network-manager or dhclient should not fail the network connection, at least not unless network manager does that. But that would be a in network-manager and should be fixed instead. A simply workaround even would be to kill it with SIGTERM to give it no chance to do any harm. -- 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
Here, I see init (expected), dhclient, dnsmasq and plymouthd. -- 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, Jan 29, 2013 at 01:47:47PM -, Daniel J Blueman wrote: Here, I see init (expected), dhclient, dnsmasq and plymouthd. plymouthd is also expected to be running but should not have any files open for writing. The other two are clearly associated with network-manager, and seem to indicate a failure to clean up. -- 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
We saw issues like this in Ubuntu 11.10 as well, and it was resolved by figuring out what is left running just before shutdown. If you can edit /etc/init.d/umountroot and add this, just before the line starting with 'mount', which on my 12.10 system is line 86: /usr/sbin/lsof -n /last-shutdown-lsof (You may need to sudo apt-get install lsof) This will record all open files just before root is remounted. Then after verifying that the FS was detected as dirty (please, stop calling it corrupt, it is not corrupt, just dirty) and fsck was run, upload the file /last-shutdown-lsof to this bug and we can take a look at it. (please check the content of that file. I don't think it will have any sensitive data in it, but please check before uploading as this bug is public). Judging from the reports, I doubt very much that this has anything to do with the kernel other than Ted T'so's suggestion that the kernel is simply exposing the dirty filesystem. -- 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 Clint, I will try and report back soon, but... For me, lsof is located at /usr/bin/lsof not /usr/sbin/lsof -- 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
Ok, here are two version of last-shutdown-lsof. last-shutdown-lsof-available-unchecked is a clean shutdown with network- manager 'available to all users' unchecked. last-shutdown-lsof-available-checked is a unclean shutdown with network- manager 'available to all users' checked. Hope this helps ** Attachment added: last-shutdown-lsof-available-unchecked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3505115/+files/last-shutdown-lsof-available-unchecked -- 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
Oops, here the other file. ** Attachment added: last-shutdown-lsof-available-checked https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3505116/+files/last-shutdown-lsof-available-checked -- 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
Russell, Your log shows dhclient holding a file open. It also shows that Network Manager itself is no longer running. Can you confirm that Network Manager is the only way dhclient is run on your system? If this dhclient is from NM, then it seems that NM is failing to correctly reap the dhclient at shutdown. Opening a task for NM. ** Changed in: network-manager (Ubuntu) Status: Invalid = Triaged ** Changed in: network-manager (Ubuntu) Importance: Undecided = High -- 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, as far as I can tell, NM is the only way that dhclient is started/run. Is there a way to confirm 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
Further to #45, if I check 'Available to all user' (usually causing an unclean filesystem at shutdown) and then do 'sudo service network- manager stop' and then 'killall dhclient' the filesystem will then go down cleanly. Steve, I'm guessing that answers your question at #44. -- 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
Clint, Here is the file last-shutdown-lsof I obtained per your instructions. It was generated on Quantal, with Enable Networking unchecked before shutdown. My list of open files looks different from Russell's one. I do not have entries for dhcp, but I do have entries for modem-manager. ** Attachment added: last-shutdown-lsof https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3505260/+files/last-shutdown-lsof -- 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 wonder if somehow dhclient is being added to omitpids. If you edit /etc/init.d/sendsigs, and uncomment the '#report_unkillable' on line 132, then reproduce agian. Then look in /var/crash for apport reports mentioning dhclient. If there are some, then its being added to the list of pids the system is not allowed to kill, but whatever has added it has not managed it 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
Clint, I have tried what you suggested (uncomment line 132 at /etc/init.d/sendsig), and caused an unclean shutdown by checking 'Available to all users' for current NM connection. On reboot, there was no mention of dhclient in /var/crash. -- 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 use wireless exclusively and tried the following combinations but NEVER achieved a clean shutdown. available to all (3 users) --- 1. autoconnect, connected @ shutdown available to single user - 2. autoconnect, connected @ shutdown 3. autoconnect, disconnected before shut 4. manually connected, disconnected before shut 5. networking + wireless enabled, but never connected 6. disabled networking, never connected 7. disabled wireless+networking, never connected My lsof log #1 mentions dhclient as others have. My logs #5 - 7 contain no suspect programs. But my logs #1 - 4 also implicate dnsmasq. I've included the logs from attempt #4 and 7 for what they're worth. ** Attachment added: disconnect wireless before shutdown https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3505332/+files/last-shutdown-lsof.4 -- 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
and here's # 7... ** Attachment added: everything disabled, never connected and still unclean shutdown https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3505333/+files/last-shutdown-lsof.7 -- 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
@Jim Warner, does your suggestion at #10 still work for you. It works for me, if I unckeck all connections, wired, wireless and mobile. -- 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
@Russell Faull, sadly no. That hasn't worked for me since the problem recurred (a few weeks ago, as I recall). Fedora (spherical cow) is looking better and better... -- 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 STILL occurs in 64 bit 1304 (Raring) with kernel 3.8.0-2-generic. Downloaded and tested today 2013-01_27 -- 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 thing actually got worse in Quantal, as the workaround become ineffective after a recently update. Now fsck runs on each and every boot, even if Enable Networking is unchecked before shutdown. Is anybody else seeing this behavior? This is the Quantal kernel I am currently running: $ uname -a Linux skinny 3.5.0-22-generic #34-Ubuntu SMP Tue Jan 8 21:47:00 UTC 2013 x86_64 x86_64 x86_64 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
Does anyone else see two lines about 'hub_port_status failed error (-110)' just before shutdown and immediately following 'mount: / is busy'? These errors always occur on several computers using different filesystems. (None of the workarounds mentioned above or in bug #1061639 resolve the problem of fsck/log replay on next boot.) Is there a way to kill all usb processes before shutdown to try and determine if the usb system is interfering with the clean unmount of the filesystem? I'm using kernel 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:05:29 UTC 2013 i686 i686 i686 GNU/Linux This may need a separate bug report, if the usb system is a possible cause and other filesystems also run fsck/log replay. -- 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 agree that this has gotten worse recently and occurs on every boot. That, along with the apparent lack of 'interest in/progress on' a solution has really affected my opinion of Ubuntu and confidence in quantal. My kernel: 3.5.0-22-generic #34-Ubuntu SMP Tue Jan 8 21:47:00 UTC 2013 x86_64 x86_64 x86_64 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
Considering the published intention to have some form of 13.04 running on a Nexus7, I would say that it is FANTASY to expect much to be fixed in 12.10 with the exception of fixes to 13.04 that can be directly backported to 12.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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 should be generalised to other file systems. It occurs using xfs and jfs, as well as ext4. In my experience the fs is not relevant, except some recover from an unclean shutdown better than others. (It's easy to try different file systems using fsarchiver, don't forget to change fstab to the new fs before reboot.) -- 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
Since one week this issue have occured again. -- 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
Richard, This bug exists in 12.10 and 13.04. In order to avoid file system corruption while using 12.10 or 13.04, you MUST disable networking before: 1. A system crash (if you have Nvidia hardware, this will be IMPOSSIBLE due to extremely poor drivers). 2. An orderly shutdown/restart. Another option is to boycott 12.10 and 13.04 until the problem is resolved. -- 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 STILL occurs in 64 bit 1304 (Raring) with kernel 3.8.0-0-generic. Downloaded and tested yesterday 2013-01_14 -- 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
Issue have disappeared since one month on a new installation of Raring 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
Add upstart task for Ubuntu. ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New ** Changed in: upstart (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- 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
Has anyone affected by this bug had a chance to test 13.04(Raring)? It would be good to know if this issue exists there as well, or if it is limited to 12.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upstart (Ubuntu) Status: New = 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
@Joseph I've tested with various v3.6 and v3.7 mainline kernel, along with Ubuntu kernels, all with defaults mount options; I still observe unclean filesystem messages: $ dmesg ... EXT4-fs (sda2): INFO: recovery required on readonly filesystem EXT4-fs (sda2): write access will be enabled during recovery ... EXT4-fs (sda2): recovery complete Users users likely mis-correlate NetworkManager as the issue, since it changes the upstart race condition timing; most likely, this is an upstart issue, as I believe the kernel has the correct behaviour, thus it would be inappropriate to add the kernel-bug-exists-upstream tag. What's next? ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags removed: needs-upstream-testing ** Also affects: upstart Importance: Undecided Status: New -- 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
We need to remove the network-manager project association, as it is just circumstantial. ** Changed in: network-manager (Ubuntu) Status: Confirmed = Invalid ** Changed in: upstart Status: New = 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
The workaround of disabling networking becomes unavailable EACH time POORLY maintained Nvidia drivers randomly cause 12.10 to crash requiring a power cycle to recover. Will this BUG be fixed before 13.04 or should I AVOID 12.10 and continue to use 12.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/ubuntu/+source/linux/+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 facing the same problem. Then I've read that by disabling networking before turning off the computer the problem disappears, however, after two days of turning turning off networking service and everything working fine, I've ran in the same issue, even having disabled networking. I am using gnome-shell and I don't have a button to disable networking but I switch the service off instead sudo service networking stop right before shutting down the system. several errors appear when I stop the networking service: 1-gnome-shell crashes and I lose the window borders including buttons to close them. 2-Also the top bar disappears and hence I need to stop the machine by sudo shutdown now. this process fails when trying to stop services and logs me in into a root terminal. to stop the machine I have to reboot now and turn off the machine manually when in starts. It is becoming urgent to solve that issue as every 2 days I need to boot with a usb drive and force a superblock correction using that tutorial. http://www.cyberciti.biz/faq/recover-bad-superblock-from-corrupted- partition/ I've been using Ubuntu since 7.04 and I am at one step to completely switch to another O.S. I cannot work with so much problems. -- 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/ubuntu/+source/linux/+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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = 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/ubuntu/+source/linux/+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 ran into this bug and confirm it that the suggested workaround is effective. The problem does not show up if I uncheck Enable Networking before shutting the system down. -- 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/ubuntu/+source/linux/+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
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/ubuntu/+source/linux/+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
To clarify as it is not completely apparent from the above discussion: The repairs reported by fsck are not caused by corruption, but are harmless and purely cosmetic fixes. The reason is that to avoid performance bottlenecks, ext4 does not update the superblock after each inode or block (de)allocation. This is done on (clean) unmount instead and only to make it look good. The filesystem does not rely on this information. The real bug is of course ubuntu not shutting down cleanly, and thus not performing the umount. Then again if this is not an error in the fs, then maybe fsck shouldn't prevent the system from cleanly booting. Theodore Ts'o take on it: https://plus.google.com/117091380454742934025/posts/JmpczpdwgrQ -- 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/ubuntu/+source/linux/+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
Hmm, somehow I missed that the actual Theodore Ts'o already commented on this here. Oops. Still though , if this is not an error in the fs, then fsck shouldn't prevent the system from cleanly booting. -- 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/ubuntu/+source/linux/+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 attempted to focus on a repeatable error condition. Essentially, a fsck via an alternate copy of Ubuntu would ALWAYS produce errors following simple behavior. Boot, logon, shutdown. If I keep the Enable Network option unchecked, the error NEVER occurs. Therefore it seems reasonable to conclude that networking functionally is broken. -- 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/ubuntu/+source/linux/+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
Might this have to do with anything relating to NetworkManager not connecting automatically or not detecting any connections until I disable the Enable Networking option, wait a couple of seconds and enable it again. Same for Wireless. Tested just in case it has something to do with it with Intel LAN Wired connections (Motherboards Intel DP35DP and Intel DZ68DB) and with Linksys WMP300N, Linksys WMP600 and Realtek Gigalan (Forgot model). All of them I need to reset the network like I mentioned above. -- 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/ubuntu/+source/linux/+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) Importance: Critical = High -- 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/ubuntu/+source/linux/+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 see a lot of log files here, but somehow e2fsck logs seem to be missing. Any chance you have captured e2fsck messages or could recreate those? And I entirely agree with you, in my opionion just updating a recent stable kernel to a development version is not a real solution. Thanks, Bernd -- 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/ubuntu/+source/linux/+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
When I checked /var/log/fsck, the two files appear unchanged from the original distribution on both the 12.10 and 12.04 OS's. I have attached a screenshot of the fsck output in case that would be helpful ** Attachment added: Screenshot of fsck output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/+attachment/3420896/+files/FSCK_Output_2012-11-01%2011%3A15%3A21.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/ubuntu/+source/linux/+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
Filesystem corruption after shutdown with a clean standard installation. 100% confirmation. 100% reproducable. But I guess it's not ext4 related. It's a dbus/networking problem with the shutdown scripts. However nobody fixed it. Though it was still reported. Busy filesystem, busy scripts, unclean shutdown. Everytime. My system: AMD64, wired Networking (forcedeth). Again, I think it's a dbus/networking/shutdown/upstart/initscripts problem. It get's triggered for some people. And it doesn't get triggered for others. That's the strange part about it. References: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1061639 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987 (it say 'Fix released', but I doubt it honestly.) -- 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/ubuntu/+source/linux/+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
Shutdown filesystem corruption in 12.10 stops for me after doing: sudo apt-get remove --purge dnsmasq-base resolvconf wpasupplicant isc-dhcp- client isc-dhcp-common libnm-glib-vpn1 libnm-glib4 libnm-gtk-common libnm-gtk0 libnm-util2 network-manager network-manager-gnome ubuntu- minimal ntp plymouth-label plymouth-theme-lubuntu-logo plymouth-theme- lubuntu-text plymouth-theme-ubuntu-text mobile-broadband-provider-info blueman bluez lubuntu-core lubuntu-desktop modemmanager obex-data-server ppp pppconfig pppoeconf rfkill wvdial mlocate (I guess mandatory are dnsmasq-base, resolconf, isc-dhcp-*, network- manager-*) -- 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/ubuntu/+source/linux/+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 too have had this problem since upgrading (not fresh installing) 12.10. Under my wireless connection, when I uncheck available to all users, for each of several users, I am able to shutdown cleanly. Of course, upon reboot the available, not connected and then connected messages are a bit anoying. I hope my experience may provide additional clues to this bugs ultimate demise. -- 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/ubuntu/+source/linux/+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 looks to be the same issue as I was experiencing during 12.10 development: http://old.nabble.com/ext4-recovery-deleted-orphans-on- reboot...-td34475175.html Journal recovery occurs 100% of the time; list of orhpan inodes presumably depends on the amount of unlinking in the last 5 seconds before shutdown. Oddly enough, I don't observe this on my work desktop running Ubuntu 12.10, but I do see this on three laptops - also with Ubuntu 12.04. I'll double-check 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/ubuntu/+source/linux/+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
Those specific fsck corrections --- fixing the number of free blocks and the number of free inodes --- is completely normal and is purely a cosmetic issue. There is nothing to worry about here. What is going on is that ext4 no longer updates the superblock after every block and inode allocation; that causes a wasteful write cycle to the superblock at every single journal commit, and it also is a SMP scalability bottleneck for larger servers (i.e., with 32 or 64 CPU's). To fix this, we no longer update these values in the superblock at every commit. Instead, we only update these values when we unmount the file system, mainly for cosmetic purposes so that dumpe2fs shoes the correct number of free inodes and blocks, and at mount time we calculate the total number of free blocks and inodes in the file system by summing the the free blocks/inodes statistics for each block group. So in fact, ext4 does not depend on the correctness of the values in the superblock, but it does try to update them on a clean unmount. In e2fsprogs commit id 2788cc879bbe6, which is in e2fsprogs 1.42. 3 and newer, we changed things so that e2fsck -n would not display this as something wrong. However, we still do show this as something that we fix when running e2fsck -y or -p, since in fact it is a change to the file systems. See: http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=commit;h=2788cc879bbe667d28277e1d660b7e56514e5b30 No one else has complained or noticed up until now, because other distro's apparently are capable of doing a clean shutdown allowing the file system to be unmounted cleanly. Ubuntu, unfortunately, is incapable of reliably doing a clean shutdown even when users request it, which is why Ubuntu users are seeing this behavior much more frequently, and apparently some people have panicked as a result. Sigh -- 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/ubuntu/+source/linux/+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
For my environment (Ethernet DSL to Internet) a temporary workaround follows: 1. UNCHECK Enable Networking 2. Wait until after the disconnected message goes away 3. Restart and Shutdown 4. Fsck from an alternate installation will NOT throw any errors. Apparently Unchecking Enable Networking does something that a simple restart or shutdown does NOT in terms of preparing for a SAFE 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/ubuntu/+source/linux/+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
Ok, I found this also on older desktops with rotational disks (all the four ones mentioned have SSDs) running Ubuntu 12.04.1. As Ted points out, it looks like Ubuntu (Upstart?) has issues with shutdown, but could there be a race exposed by the superb speed that Upstart is executing the umount/remount-ro, disk-cache-flush and kernel- reboot vector sequence? -- 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/ubuntu/+source/linux/+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: New = 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/ubuntu/+source/linux/+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
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages. Once you've tested the upstream kernel, please remove the 'needs- upstream-testing' tag. Please only remove that one tag and leave the other tags. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc2-raring/ ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Changed in: linux (Ubuntu) Importance: High = Critical ** Tags added: kernel-da-key needs-upstream-testing -- 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/ubuntu/+source/linux/+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
Set importance to critical due to possible corruption. -- 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/ubuntu/+source/linux/+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
Are you using any Non-default mount options? -- 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/ubuntu/+source/linux/+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 an effort to KISS and minimize regression testing, I reported a 100% repeatable bug. In my haste, I failed to indicate that the source iso used burn the LiveCD was the 64-bit version of Ubuntu 12.10 which was recently released to the public. After running the installation under the Try Ubuntu path, I performed a shutdown followed by a reboot of an alternate version (12.04) of Ubuntu. A fsck -vf of the recently installed (12.10) indicated problems and I followed the prompts to repair the Ext4 file system. Acronis True Image Home 2013 was used to create an image which could be restored quickly. To create the problem, I booted (12.10), logged in, waited a while (sometimes a few minutes) and then performed a shutdown followed by a reboot of an alternate version (12.04) of Ubuntu. A fsck -vf of the recently installed (12.10) indicated problems and I followed the prompts to repair the Ext4 file system. It would seem to me that critical data can be obtained from a 100% repeatable problem in a known environment. The symptoms might be masked in a different version of the kernel although the problem still exists. -- 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/ubuntu/+source/linux/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
