Bug 4883

Summary:	Running a VMware Virtual Machine on an NTFS partition causes ntfs-3g to go to 100 percent CPU
Product:	Mageia	Reporter:	Andy Liebman <AndrewL733>
Component:	RPM Packages	Assignee:	Anssi Hannula <anssi.hannula>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Normal	CC:	nic
Version:	Cauldron	Keywords:	NEEDINFO, Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	ntfs-3g	CVE:
Status comment:

Description Andy Liebman 2012-03-11 20:09:01 CET

I run a triple boot Macbook Pro 8,1 (OS X Lion, Windows 7 64-bit, and Linux -- currently Mageia 2 Beta 1 64bit).  I have 8 GB of RAM. This is a Core i7 2.6 Ghz machine with 4 cores/8 threads. 

Because I need to access the same Virtual Machines from all operating systems, I have traditionally put the VMs on a separate NTFS "Data" partition (and used the latest Paragon NTFS from OS X, because it outperforms ntfs-3g for OS X).  

ntfs-3g has never given me any issues in Linux and in fact until 3 weeks ago I was running the above configuration with Mandriva 2011 on this same triple boot Macbook Pro. 

However, now with Mageia 2 Beta 1, if I try to run a VMware VM from an NTFS partition, top quickly shows that mount.ntfs-3g goes to 100 percent cpu and stays there.  The VM basically hangs (if I am very patient and wait about 10 minutes, I can close it cleanly).  If I copy the same VM to an EXT4 partition, it runs fine. 

I had the same issue with the 3.2.9 kernel and the 3.3.0-rc6 kernel.

How can I help troubleshoot this?  Is there a problem with ntfs-3g in this version of Mageia?

Comment 1 Manuel Hiebel 2012-03-11 21:35:58 CET

Hi, thanks for reporting this bug.
Anssi any ideas ?

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => anssi.hannula
Source RPM: (none) => ntfs-3g

Comment 2 Marja Van Waes 2012-05-26 13:04:02 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 3 Marja Van Waes 2012-07-06 15:05:13 CEST

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Comment 4 Nic Baxter 2015-02-10 00:29:04 CET

I have been unable to replicate this bug.
Using 
VirtualBox 4.3.20_OSE r 96996
ntfs-3g-2014.2.15-4.mga5
kernel-desktop-3.18.2-1.mga5-1-1.mga5

So will change status.

Status: NEW => RESOLVED
CC: (none) => nic
Resolution: (none) => WORKSFORME