umountfs doesn't cleanly unmount / on reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Lucid |
Invalid
|
Undecided
|
Unassigned | ||
Maverick |
Invalid
|
Undecided
|
Unassigned | ||
Natty |
Invalid
|
Undecided
|
Unassigned | ||
Oneiric |
Invalid
|
High
|
Unassigned | ||
sysvinit (Ubuntu) |
Fix Released
|
High
|
Clint Byrum | ||
Lucid |
Won't Fix
|
High
|
Unassigned | ||
Maverick |
Invalid
|
High
|
Unassigned | ||
Natty |
Fix Released
|
High
|
Canonical Foundations Team | ||
Oneiric |
Fix Released
|
High
|
Clint Byrum |
Bug Description
Binary package hint: initscripts
Sometimes (ca. 50% of cases) when rebooting or turning off the computer, the console shows shortly before shutting down (analogous; plymouth disabled):
[...]
unmounting weak filesystems ...
mount: / is busy
[...]
At next reboot, my root filesystem is recognised as needing recovery, e.g.:
[ 2.720951] EXT4-fs (sda5): INFO: recovery required on readonly filesystem
[ 2.721033] EXT4-fs (sda5): write access will be enabled during recovery
[ 4.925307] EXT4-fs (sda5): orphan cleanup on readonly fs
[ 4.939550] EXT4-fs (sda5): ext4_orphan_
[ 4.952641] EXT4-fs (sda5): 1 orphan inode deleted
[ 4.952696] EXT4-fs (sda5): recovery complete
[ 5.717403] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: initscripts 2.87dsf-4ubuntu17
ProcVersionSign
Uname: Linux 2.6.35-14-generic i686
Architecture: i386
Date: Wed Aug 11 12:17:27 2010
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=de_DE.utf8
SHELL=/bin/bash
SourcePackage: sysvinit
Changed in sysvinit (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
tags: | added: lucid-amd64 |
Changed in sysvinit (Ubuntu): | |
milestone: | none → oneiric-alpha-1 |
status: | Confirmed → Triaged |
tags: | added: patch |
Changed in sysvinit (Ubuntu): | |
assignee: | nobody → Clint Byrum (clint-fewbar) |
Changed in sysvinit (Ubuntu): | |
milestone: | oneiric-alpha-1 → oneiric-alpha-2 |
Changed in sysvinit (Ubuntu): | |
status: | Triaged → In Progress |
Changed in mountall (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in mountall (Ubuntu Lucid): | |
status: | New → Invalid |
Changed in mountall (Ubuntu Maverick): | |
status: | New → Invalid |
Changed in mountall (Ubuntu Natty): | |
status: | New → Invalid |
Changed in sysvinit (Ubuntu Lucid): | |
status: | New → Triaged |
Changed in sysvinit (Ubuntu Maverick): | |
status: | New → Triaged |
Changed in sysvinit (Ubuntu Natty): | |
status: | New → Triaged |
Changed in sysvinit (Ubuntu Lucid): | |
importance: | Undecided → High |
milestone: | none → ubuntu-10.04.3 |
Changed in sysvinit (Ubuntu Maverick): | |
importance: | Undecided → High |
Changed in sysvinit (Ubuntu Natty): | |
importance: | Undecided → High |
Changed in sysvinit (Ubuntu Natty): | |
assignee: | nobody → Canonical Foundations Team (canonical-foundations) |
tags: |
added: verification-done removed: verification-needed |
tags: | added: quantal |
This happens almost constantly to me, using Kubuntu 10.04. It occurs on both my laptop and desktop and I am afraid of data loss or corruption.
Is there any workaround?