Same here on Maverick. In fact it uses 45-50% of CPU, xorg 15-25% and
nautilus 15% in total 85-90%. I was copying files for 15 minutes, at one
moment I thought that my laptop will melt from the heat. I really don't
understand why this bug is marked as Invalid.
--
You received this bug notificatio
PS: Home folder about 30GB, VirtualBox about 10GB. The whole process got
stuck when the loopback file was about 13GB.
--
mount.ntfs causes 100% CPU (iowait)
https://bugs.launchpad.net/bugs/328352
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Same problem here.
I have a 500GB USB external drive and wanted to keep it NTFS. I also
wanted to copy my full home directory from one computer to the other. I
created an ext4 loopback file on the NTFS and started coping. When I
reached to VirtualBox image on my home directory it got stuck.
Afterw
I've experienced a very similar problem Ubuntu 9.10. copying a large
file from ext4 filing system to USB ntfs drive (23GB). mount.ntfs
consuming 85-95% + of CPU most of which is %user. iostat 6 100 shows
writes at 83/sec or less. It will succeed eventually but will probably
take best part of 24
** Also affects: ntfs-3g (Debian)
Importance: Undecided
Status: New
--
mount.ntfs causes 100% CPU (iowait)
https://bugs.launchpad.net/bugs/328352
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Oh and I forgot to mention that the problem arises ONLY after the
mentioned amount of somewhere around 4,4 GB were written. Before that
point everything is fine. But as the file grows, the CPU usage suddenly
jumps up.
--
mount.ntfs causes 100% CPU (iowait)
https://bugs.launchpad.net/bugs/328352
Y
I can tell you how to reproduce it easily: It has todo with the
filesize.
Try to copy a file which is larger than 4.X GB and the CPU usage bumps
up to > 90%.
I can safely reproduce it. Leech a file (lets say 5 GB) - CPU usage 90%. Stop
it - CPU usage normal. Restart it CPU usage 90%.
Stop it and
Thanks for the explanation, Szabolcs.
I can't remember the exact details now of course, but I do remember that
the 'dd' copy from USB to /dev/sda2 had finished when I spotted the CPU
monitor showing the I/O wait.
I hadn't spotted mount.ntfs in the process list previously, although
admittedly I'd
It's impossible to see what NTFS-3G has to do with the problem.
Yes, the /dev/sda1 NTFS partition is mounted at /media/WindowsRecovery
by NTFS-3G but you were reading from another file system mounted at
/media/mobile120 and writing to partition /dev/sda2.
The IOWAIT is completely normal when one
Copying is clear enough:
"I was copying an NTFS partition image using dd from an external USB
hard-drive to /dev/sda2 (after replacing the laptop's internal hard-
disk)."
E.g. dd if=/media/mobile120/vista.img of=/dev/sda2
The file being copied was 29GB.
I mentioned it simply because it might be
It's not clear what you copied from where to where and how.
Anyway it looks to be a hardware problem. Check your RAM and disks for
bad sectors, e.g. by the utility badblocks.
--
mount.ntfs causes 100% CPU (iowait)
https://bugs.launchpad.net/bugs/328352
You received this bug notification because
11 matches
Mail list logo
