[Bug 711799] Re: e2fsprogs wrongly identifies ext4 as mounted

[Philipp Gampe]

I now tried in single user mode and there I could run the check. It even
said it was clean? (Looking at what tune2fs said, that is - for me -
surprising).

I did run lsof on the partition, but it did not return anything.
It might have been an unclean shutdown of gparted, leaving either parted or ntfsresize as zombies on /dev/sdb. That happened today, but was visible in lsof. But yesterday I did not run fdisk -l, which is quite useful to see more information on what the kernel knows.

I also run the check with the -c option, but no error was mentioned.
Everything turned out the be clean.

I then removed /dev/sdb1 from /etc/fstab and continued to boot normal.
Then I could change the size of the partition (that was my initial
goal). Afterwards I added it back and all seems to run smooth now.

So if anyone runs into the same problem, here is what to check:
0. umount /dev/sdb1; mount |grep sdb1
1. lsof /dev/sdb1
2. fdisk -l
3. cat /proc/mounts

4. remove partition from /etc/fstab and boot into single user mode
(press e on grup and add "single" at the end of the kernel line, then
press ctrl-x to boot). There check again.

5. If all fails, come back here ask again :)

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

Title:
  e2fsprogs wrongly identifies ext4 as mounted

Status in “e2fsprogs” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: e2fsprogs

  After a crash of Ubuntu netbook, the machine hang with initramfs (I
  have a /boot and /).
  Booting with the same system (ubuntu 10.10) from thumb drive, I cannot fsck it:
  $ sudo fsck /dev/sda2
  fsck from util-linux-ng 2.17.2
  e2fsck 1.41.12 (17-May-2010)
  fsck.ext4: Device or resource busy while trying to open /dev/sda2
  Filesystem mounted or opened exclusively by another program?

  But it is not mounted:
  $ cat /proc/mounts
  shows that it is not mounted; and it can't be unmounted.

  dmesg knows what is going on:
  $ dmesg | grep sda2
  [    6.513953]  sda: sda1  [01;31m [Ksda2 [m [K sda3 < sda5 > sda4
  [    9.300388] EXT4-fs ( [01;31m [Ksda2 [m [K): INFO: recovery
  required on readonly filesystem
  [    9.300398] EXT4-fs ( [01;31m [Ksda2 [m [K): write access will be
  enabled during recovery
  [    9.312706] EXT4-fs warning (device  [01;31m [Ksda2 [m [K):
  ext4_clear_journal_err: Filesystem error recorded from previous mount:
  IO failure
  [    9.312729] EXT4-fs warning (device  [01;31m [Ksda2 [m [K):
  ext4_clear_journal_err: Marking fs in need of filesystem check.
  $
  But this fsck does never materialise, and can't be done manually.

  Finally, I tried to delete the journal, but to no avail, the "Device
  or resource busy" stays. Is there any way to trick fsck into believing
  me that it is not mounted?
  If not, I still consider the behaviour somewhat wrong: if not in
  /proc/mount, why does fsck say so?
  And when I
  sudo mount /dev/sda2 /mnt
  it starts the mount process, but never finishes, and also it is
  impossible to ever exit this process, I tried with Ctrl-C, Ctrl-Z, and
  even with kill -9 from another console. Ubuntu isn't even able to shut
  down then, but keeps trying forever.

  In a nutshell, it is a bug in 10.10. I use the installer-CD written to the thumb drive (Startup Disk creator).
   Confirmed: Because when I boot with a 9.04 thumb drive, I can easily open a terminal and run fsck. Done and over.

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