The current network setup is:
--------------------------
Settings for eth2:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: umbg
Wake-on: d
Current message level: 0x00000007 (7)
Link detected: yes
--------------------------
The mii-tool - known to show the wrong speed on CentOS, shows the following:
--------------------------
eth2: negotiated 100baseTx-FD flow-control, link ok
--------------------------
The speed on the switch port is set for 1000/Full - Autonegotiation enabled
What about the "flow-control" - do I need that?
In this specific Linux system I do backup a lot of inages - all the same size - small files. I have yet to destroy a tape - this is been running for a while now.
Thank you
Main Topics
Browse All Topics





by: squifyPosted on 2009-04-26 at 23:18:18ID: 24239212
Hi,
I would try and set the NIC's on the client, backup server, switch to Auto Negotiate. The client's NIC will not transmit data until it can negotiate transfer at 1000MB. By changing them all to Auto Negotiate you will get data transferring regardless of the negotiated speed.
Also look at the type of data you are coping. If all the files are many small files and are at varying path depths you will get slower backup speeds. If you have a few large files you will get good speeds. You also have issues if you only have one client running at 10MB/s transferring to a LTO3 tape library that must be run at 80MB/s. If the tape library does not get data at that rate consistently it will think the job has finished and rewind the tape. This is called shoe-shining and will ruin your tapes and drives in a matter of months.
Let me know how changing the network speed helps.