Freeze when safely remove a NTFS disk

Bug #867811 reported by Niclas Lockner
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I have an external NTFS disk connected via USB, and when I safely remove the disk (using "Safely remove" on the dash) the system freezes completely.
Alt+sysrq+b does nothing. And after a hard restart, I get no crash report telling me that the system crashed.

If I choose to unmount the disk instead of safely remove it, or if I mount and unmount it manually using the terminal, the system does not crash.

gvfs is handling the mounting of the disk.

Entry in `mount` output:
/dev/sdb1 on /media/Film type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096,default_permissions)

I have not been able to test if this is NTFS only, or if the crash occurs with other file systems as well.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-12-generic 3.0.0-12.19
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: niclas 2319 F.... pulseaudio
 /dev/snd/controlC0: niclas 2319 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0400000 irq 46'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,1025021e,00100202 HDA:11c11040,1025021e,00100200'
   Controls : 23
   Simple ctrls : 13
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
   Mixer name : 'Nvidia GPU 0a HDMI/DP'
   Components : 'HDA:10de000a,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
Date: Tue Oct 4 21:11:57 2011
HibernationDevice: RESUME=UUID=7ca1f62e-c857-43f5-8daa-bd0db599f86a
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817)
MachineType: Acer Aspire 5739G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=4ec53029-e289-43ef-9184-22d5c03447cd ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2011-09-28 (6 days ago)
dmi.bios.date: 12/21/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.3311
dmi.board.name: JM50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvrV1.3311:bd12/21/2009:svnAcer:pnAspire5739G:pvrNotApplicable:rvnAcer:rnJM50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5739G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer

Revision history for this message
Niclas Lockner (niclasl) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Niclas Lockner (niclasl)
description: updated
Niclas Lockner (niclasl)
description: updated
Revision history for this message
Nicolás Abel Carbone (nicocarbone) wrote :

I am having this problem in Ubuntu 11.10 amd64, also with a NTFS disk. I think this bug deserves a high priority, probably even more if it have the potential of corrupting data. Is it safe to unmount instead of "Safely remove"?

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Niclas Lockner (niclasl) wrote :

Tested with ext4 and fat32. No crash, so it seems to be isolated to NTFS.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@Niclas

I noticed you upgraded to Oneiric on 2011-09-28. Were you having this issue before you upgraded?

Also, Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . The latest upstream kernel is at: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-rc9-oneiric .

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

tags: added: needs-upstream-testing
Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

This might actually be fixed with 3.0.6-stable (also available in the mainline ppa) - so if it's possible, please test that one as well.

Revision history for this message
Nicolás Abel Carbone (nicocarbone) wrote :

I couldn't try the upstream kernels. Both of them (3.1-rc9 and 3.0.6-stable) failed to boot on my PC, with the following error:

"BUG: unable to handle kernel paging request at ffff8800e0073b20"

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@Julian

Is there a specific patch in 3.0.6-stable that you can reference?

Revision history for this message
Julian Wiedmann (jwiedmann) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for the information, Julian.

It looks like that patch is for ext3/ext4 filesystems. @Niclas, I believe you confirmed this only happens with NTFS?

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.0.0-12.20)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.0.0-12.20
Revision history for this message
Niclas Lockner (niclasl) wrote :

@Joseph
"I noticed you upgraded to Oneiric on 2011-09-28. Were you having this issue before you upgraded?"
I'm almost certain that I did a fresh install from a daily image instead of upgrading from Natty.
I can't tell when the bug started to occur since I usually never disconnect the NTFS disk.
If it is to any help, I could download and run a live CD of Natty and test?

"I believe you confirmed this only happens with NTFS?"
When I excluded ext4 and fat32 I used a USB stick to do some quick testing. I now did some new tests with the same USB stick and I found that regardless of the file system used (tested ext2/3/4, fat, ntfs), the system didn't freeze when the stick was safely removed. Of course I should have taken the time to test the stick with NTFS from the start. Sorry for the confusion.
I can therefore no longer say that it is NTFS only since I can only reproduce the freeze using my external hard drive (which I unfortunately cannot reformat and test with other file systems).

I've tested with the upstream kernels that you gave me and I could not boot any kernels at all from 3.0.5 up to 3.1rc9. I never came past the plymouth screen. After booting into onerics kernel again, I received the paging request error from Apport mentioned above by Nicolás.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Niclas Lockner (niclasl) wrote :

Still present with kernel 3.0.0-12.20

Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

Niclas:
bug 844957 (comment #20) has a kernel that pulls back only the commit I mentioned a couple of days ago. Hopefully this one boots successfully on your system.

Please consider opening a seperate bug for the boot failure with 3.0.6, so the offending commit can be identified and reverted before it hits oneiric-updates.

Revision history for this message
Niclas Lockner (niclasl) wrote :

That kernel boots and it fixes the problem!

Revision history for this message
thermionix (thermionix) wrote :

Upgrading to 3.0.6 kernel has fixed this for me;
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.6-oneiric/

duplicate bug also @ Bug #878294

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.