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
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
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
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
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
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,
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
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
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
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
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.
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
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
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
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,
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
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
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
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.
**
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
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
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,
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
@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:
@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.
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
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:
$
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
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
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
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
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
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
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
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
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
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.
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:
@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
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
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
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
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
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.
** 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
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
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
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
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
** 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
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,
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
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 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
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
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
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
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
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
** 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
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
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
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
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
101 - 177 of 177 matches
Mail list logo
