I'm unable to reproduce this. On all my systems NetworkManager shuts
down cleanly and indeed doesn't stop dhclient, but that's "expected"
behavior, since when you're turning NM off you may wish to retain wired
connections, which happens to indeed be the case for users with mounted
network shares.
Is there anything else that's special with your installation which could
explain this being an issue?
** Changed in: network-manager (Ubuntu Precise)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
Incomplete
Status in “network-manager” source package in Precise:
Incomplete
Bug description:
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to
remount the root filesystem read-only, the remount fails. The
message:
mount: / is busy
is seen in the console, and the filesystem must be recovered at boot
time:
[ 8.946427] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 8.947057] EXT4-fs (sda1): write access will be enabled during recovery
[ 11.234075] EXT4-fs (sda1): recovery complete
If shared libraries used by dhclient are updated before the reboot,
orphaned inodes associated with the .so files are created. For
example, doing "sudo apt-get install --reinstall libc6" and then
rebooting leads to:
[ 8.356521] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 8.356521] EXT4-fs (sda1): write access will be enabled during recovery
[ 8.716544] EXT4-fs (sda1): orphan cleanup on readonly fs
[ 8.716544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313749
[ 8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313733
[ 8.724544] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 313725
[ 8.724544] EXT4-fs (sda1): 3 orphan inodes deleted
[ 8.728544] EXT4-fs (sda1): recovery complete
This is network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
running under 12.04. I don't believe any actual data loss will occur
as a result of this bug, but it's likely to produce much user anxiety.
Also see Bug 952315, which misidentifies the cause of the problems as
upstart.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Mar 23 07:42:20 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-03-02 (20 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/963106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
