Re: [MooseFS-Users] why master can't server any request at every o'clock?

[彭智希 <pen...@16...>]

Hi
the information of ethtool as below:
[root@mfs-CNC-GZSX-231 mfs]# ethtool bond0
Settings for bond0:
        Supported ports: [ ]
        Supported link modes:   Not reported
        Supported pause frame use: No
        Supports auto-negotiation: No
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: 2000Mb/s
        Duplex: Full
        Port: Other
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Link detected: yes


[root@mfs-CNC-GZSX-231 mfs]# ethtool bond0:1
Settings for bond0:1:
        Supported ports: [ ]
        Supported link modes:   Not reported
        Supported pause frame use: No
        Supports auto-negotiation: No
        Advertised link modes:  Not reported
        Advertised pause frame use: No
        Advertised auto-negotiation: No
        Speed: 2000Mb/s
        Duplex: Full
        Port: Other
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: off
        Link detected: yes






At 2016-03-02 17:44:46, "Aleksander Wieliczko" <ale...@mo...> wrote:
Hi,
It's look really bad. You receiving wrong packages sizes from master.
You have some serious network problems.
This is the first time when we see such a log entry!

Feb 29 13:32:37 localhost mfschunkserver[9920]: (read) packet too long (1330533152/100000)

Please check all network components - even hardware (NIC card and RAM).
I can also suggest to check MTU size - network cards and switch.

We are waiting for your reply.


Best regards
Aleksander Wieliczko
Technical Support Engineer
MooseFS.com