Mounting as minix can block a long time

Bug #1185521 reported by Removed by request
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

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.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-12-generic.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sworddragon 1569 F.... plugin-containe
 /dev/snd/pcmC0D0p: sworddragon 1569 F...m plugin-containe
 /dev/snd/timer: sworddragon 1569 f.... plugin-containe
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xf9ff4000 irq 16'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,18497662,00100101'
   Controls : 36
   Simple ctrls : 18
CurrentDmesg:
 Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file or directory
 dmesg: write failed: Broken pipe
DistroRelease: Ubuntu 13.10
EcryptfsInUse: Yes
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: [Errno 2] No such file or directory
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=05338ff8-a226-421b-90a4-1dd45199f783 ro
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
RfKill: Error: [Errno 2] No such file or directory
Tags: saucy
Uname: Linux 3.11.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo wireshark
WifiSyslog:

dmi.bios.date: 02/05/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.asset.tag: BC5FF4739C55
dmi.board.name: 960GM/U3S3 FX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd02/05/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM/U3S3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Phillip Susi (psusi)
affects: util-linux (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1185521

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Removed by request (removed3425744) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected saucy
description: updated
Revision history for this message
Removed by request (removed3425744) wrote : ArecordDevices.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : HookError_source_linux.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : Lspci.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : PciMultimedia.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : ProcModules.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : UdevDb.txt

apport information

Revision history for this message
Removed by request (removed3425744) wrote : UdevLog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc4-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Removed by request (removed3425744) wrote :

Booting with the upstream kernel works fine but the console will be permanently black.

tags: added: kernel-unable-to-test-upstream
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1185521

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Sworddragon, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

tags: added: bios-outdated-1.40
tags: added: bot-stop-nagging
Changed in linux (Ubuntu):
importance: Medium → Low
status: Confirmed → Incomplete
Revision history for this message
Removed by request (removed3425744) wrote :

Minix doesn't hang anymore on heavy disk operations and it also doesn't need longer to detect the failure than other filesystems (my system BIOS is also up to date with version 1.40).

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
tags: removed: bios-outdated-1.40
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.