kernel-packages team mailing list archive

[Launchpad Bug Tracker <1185521@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

I'm using Ubuntu 13.10 dev with mount 2.20.1-5.1ubuntu8. Forcing to use
minix as filesystem on mounting a device which has another filesystem
and doing another disk operation on the physical device will cause mount
to block until the disk operation is finished. Here is an example:

1. As preparation clean the cache with "echo 3 > /proc/sys/vm/drop_caches".
2. Execute "mount -t minix -v /dev/sda5 /mnt & find / > /dev/null" (dev/sda5 is a swap partition and / is /dev/sda1 (ext4)).

Because /dev/sda5 is a swap partition theoretically the mount operation
should fail in a short time. But mount waits until the find command has
finsihed which can need a long time. After this the following error is
shown (as expected):

root@ubuntu:~# mount: wrong fs type, bad option, bad superblock on /dev/sda5,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


Replacing minix with ext4 on mounting works fine. The mounting operation will fail too but this needs less than a seconds instead of a few minutes. It is even conspicuous that without another disk operation mounting as minix needs a few times longer than other filesystems. I'm assuming there is something broken on the minix module with checking for bad filesystems.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Mounting as minix can block a long time
https://bugs.launchpad.net/bugs/1185521
You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.