Filesystems don't get always unmounted properly at shutdown
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upstart (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Hello,
during system startup in at least 50% of the cases I see (when booting without Plymouth) messages from FSCK about recovering the journal and cleaning up orphaned inodes on my /home partition. Also shutdown on my systems takes unusually long and often ends with a message like "mount: / is busy" (displayed for a very short time).
The symptoms are similar to the ones users are (still) describing in bug #1061639 .
My harddisk is partitioned as LVM, all logical volumes (except Swap) are formatted as Ext4.
Is there anything I can do to debug an error like this in Upstart?
Kind regards,
Jan
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: upstart 1.5-0ubuntu9
ProcVersionSign
Uname: Linux 3.5.0-22-generic x86_64
NonfreeKernelMo
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
CheckboxSubmission: b37fefbc97df4ba
CheckboxSystem: 4ed15c40009aa6f
Date: Sun Jan 20 21:09:53 2013
InstallationDate: Installed on 2012-10-12 (100 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121012.2)
MarkForUpload: True
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
| Jan Rathmann (kaiserclaudius) wrote | #1 |
| Jan Rathmann (kaiserclaudius) wrote | #2 |
| Jan Rathmann (kaiserclaudius) wrote Re: [Bug 1102151] Re: Filesystems don't get always unmounted properly at shutdown | #3 |
If I manually stop NetworkManager via 'sudo service stop network-manager' before shutting down or restarting my computer, my /home partition will get umountet properly as it seems (no "recovering journal" message after reboot). So this bug seems to be related somehow to NetworkManager.