В Tue, 12 May 2015 13:09:18 -0400
Greg Freemyer
On Tue, May 12, 2015 at 12:52 PM, Greg Freemyer
wrote: I do a lot of heavy USB-3 disk i/o, but today I'm throwing in a drive connected via eSata.
This is with a laptop that I use all the time for disk i/o intensive tasks.
I've got the equivalent of:
dd if=/dev/eSata_drive of=/dev/USB3_drive bs=4kb
going on. (I don't know what bs my app is actually using.)
My throughput is around 38 MB/sec which is surprisingly slow, but not crazy slow.
More surprising is the laptop otherwise acts almost frozen. I had done some work on another USB-3 drive. I issued a "umount" command to it about 15 minutes ago and it still hasn't unmounted.
Or at least I don't think it has. I can't even use alt-F2 or contrl-alt-F2 to get back to the virtual console.
I had also tried to log into virtual console 4. After 5 minutes it had not logged in.
As it stands the only thing I can do is observe virtual console 3. I'm getting status updates and it claims my copy task will be done in 45 minutes or so.
I hope so, I'd like to be able to use that PC again.
10 minutes later and I can move between virtual consoles again. And the umount completed.
But the machine is still very non-responsive to anything disk i/o related.
Does "dd ... oflag=direct" make any difference? What /proc/meminfo says when this happens? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org