Linux Format forums

[nordle]

I have two disks on primary controller, PATA, master+slave by jumper.

I'm in the process of copying 10GB of opensuse goodness from hdb to a samba share on another machine via konqueror's url smb://servername/sharename/dir

Konq has two tabs, local tree and smb tree, and I just did a right click copy and paste.

What is strange, I noticed that gkrellm was showing 15MB/sec throughput on both hdb and 12MB/sec on hda (both drives on original machine).
If this is true, then its a bizarre waste of power, resources, time etc I mean, does the data seriously have to go from hdb to hda then to the remote server, that seems very odd.

Is this real? How can I check that this is truly happening and its not some weird little bug in gkrellm?

If its real, does anyone know if its supposed to be like that or could it be:
- Hardware bug (mobo's disk controller being weird)
- KDE bug
- samba bug
- kernel bug
etc

Thanks for any suggestions.

[wyliecoyoteuk]

Depends on how your PC (and NIC, and Samba) is setup, there could be temporary buffer somewhere on hda
_________________
The sig between the asterisks is so cool that only REALLY COOL people can even see it!

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

[ollie]

Remember Konqueror is running from hda, as is the graphics display drivers, everytime you do something it has to be processed by an application. Also, is your swap file on hda? If your RAM is being pushed into swap file space whilst files are being loaded and moved you will have disk activity.

[nordle]

This machines has 1GB of RAM, swap never gets used. I think what it is, is /proc I think /proc/copy_process_number/fd has the file copied and stored as it goes along, then when the process is finished its released again.

I don't think its a bug, but equally i'm not sure it makes a lot of sense.
_________________
I think, therefore I compile

[wyliecoyoteuk]

Probably a FIFO pipe, acting as a cache for the network card.
In any transfer there is a "send" buffer on the transmitting pc, and a "receive" buffer at the other end.
The "send" buffer queues read packets for transmission, the "receive" buffer queues received packets for disk write.
Looks like /proc is where the pipe lives.

(Yes, this is a gross simplification)
_________________
The sig between the asterisks is so cool that only REALLY COOL people can even see it!

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

[nordle]