I am seeing this too in the last couple of reboots. My / and home are on 
separate lvm volumes and share the same crypted luks partition. /home is 
actually bind-mounted from my data partition:
/dev/mapper/ssd-root                                            /               
ext4    noatime,errors=remount-ro,discard 0       1
/dev/mapper/ssd-data                                            /data   ext4    
noatime,discard 0       3
/data/home                                                                      
/home   none    bind    0       0

fsck from util-linux 2.20.1
fsck from util-linux 2.20.1
/dev/mapper/ssd-root: clean, …
/dev/mapper/ssd-data: Clearing orphaned inode …

Kernel is 3.2.0-36-generic #57 amd64.

I am have enabled the standard precise repo, precise-updates, precise-
backports, precise-security, partner (and all sections in each of them,
i.e. main restricted universe multiverse), but *not* precise-proposed. I
am also using the official opera and mate-desktop repository (I am
running mate as DE). I have also added the quantal repo to use the
updated texlive packages, but this should be not related, everything
else is pinned back.

The purpose of this paragraph is to isolate the offending package. I dont think 
that the packages named inhere are related; they are just named to derive a 
timeframe when it broke. I have to admit that I saw this problem earlier (as in 
months ago) too, but I am quite certain this is something new, i.e. introduced 
in 2013. 
The last updates I installed are firefox-globalmenu 
18.0.1+build1-0ubuntu0.12.04.1 (automatically, last night), desktop-file-utils 
0.20-0ubuntu3 (manually, 2013-01-18). The non-security updates between the two 
just mentions have not been installed yet, but I will do so now. The problem 
was certainly introduced by an update *before* them (or a security update).

There was a NM update on the 16th:  network-manager:amd64 0.9.4.0-0ubuntu4.1 -> 
0.9.4.0-0ubuntu4.2, at the same time I upgraded xserver and 
activity-log-manager-common (whatever that is :) and a few others.
On the 13th I upgraded mountall:amd64 2.36 -> 2.36.3,  grub2-common:amd64 
1.99-21ubuntu3.4 -> 1.99-21ubuntu3.7 (et al) and a few others. I would guess 
the culprit is one of those above.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103416

Title:
  12.04 isn't cleanly unmounted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1103416/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to