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 never been looking for it. I tend to be looking at top or
"ps -ef | grep ..." output much of the time.
I'm wondering if what I saw was the results of the 'dd' copy failing
because the USB device had an error. I didn't notice any dd error since
I'd had that running in the background because it takes a while - I'd
gone off to do others things.
>From your explanation it looks like my linkage of the issue with
mount.ntfs was a result of coincidence.
Since I can't reproduce it I'll mark the report invalid. Thanks for your
input.
** Changed in: ntfs-3g (Ubuntu)
Status: New => Invalid
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
