Re: [Aoetools-discuss] end_request: I/O error
Brought to you by:
ecashin,
elcapitansam
Menu
▾
▴
Re: [Aoetools-discuss] end_request: I/O error
|
From: Daofeng Li <li...@gm...> - 2015-06-17 05:11:40
|
Probably my MTU is too high? Thanks again. # aoe-sancheck Probing...skipping eth3, discover failure: Network is down skipping eth1, discover failure: Network is down done. ========================================== INTERFACE SUMMARY ========================================== Name Status MTU PCI ID eth0 UP 1500 14e4:163a eth1 DN 1500 14e4:163a eth2 UP 9000 14e4:164f eth3 DN 1500 14e4:164f ========================================== DEVICE SUMMARY ========================================== Device Macs Payload Local Interfaces e50.0 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.1 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.2 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.3 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.4 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.5 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.6 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.7 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.8 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.9 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.10 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.11 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.12 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.13 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.14 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.15 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.16 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.17 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.18 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.19 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.20 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.21 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.22 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e50.23 1 11776 eth2 The path eth2->002590048ba3 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.0 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.1 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.2 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.3 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.4 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.5 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.6 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.7 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.8 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.9 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.10 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.11 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.12 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.13 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.14 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.15 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.16 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.17 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.18 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.19 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.20 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.21 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.22 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload e52.23 1 15872 eth2 The path eth2->003048dea511 is only capable of 1024 byte payloads eth2: MTU (9000) not set optimally for device's capable payload Daofeng On Wed, Jun 17, 2015 at 12:07 AM, Daofeng Li <li...@gm...> wrote: > Dear all, what does this kickme means? Thanks. > > # aoe-stat > e50.0 1000.204GB eth2 8704 up,kickme > e50.10 1000.204GB eth2 8704 up,kickme > e50.1 1000.204GB eth2 8704 up,kickme > e50.11 1000.204GB eth2 8704 up,kickme > e50.12 1000.204GB eth2 8704 up,kickme > e50.13 1000.204GB eth2 8704 up,kickme > e50.14 1000.204GB eth2 8704 up,kickme > e50.15 1000.204GB eth2 8704 up,kickme > e50.16 1000.204GB eth2 8704 up,kickme > e50.17 1000.204GB eth2 8704 up,kickme > e50.18 1000.204GB eth2 8704 up,kickme > e50.19 1000.204GB eth2 8704 up,kickme > e50.20 1000.204GB eth2 8704 up,kickme > e50.2 1000.204GB eth2 8704 up,kickme > e50.21 1000.204GB eth2 8704 up,kickme > e50.22 1000.204GB eth2 8704 up,kickme > e50.23 1000.204GB eth2 8704 up,kickme > e50.3 1000.204GB eth2 8704 up,kickme > e50.4 1000.204GB eth2 8704 up,kickme > e50.5 1000.204GB eth2 8704 up,kickme > e50.6 1000.204GB eth2 8704 up,kickme > e50.7 1000.204GB eth2 8704 up,kickme > e50.8 1000.204GB eth2 8704 up,kickme > e50.9 1000.204GB eth2 8704 up,kickme > e52.0 1000.204GB eth2 8704 up,kickme > e52.10 1000.204GB eth2 8704 up,kickme > e52.1 1000.204GB eth2 8704 up,kickme > e52.11 1000.204GB eth2 8704 up,kickme > e52.12 1000.204GB eth2 8704 up,kickme > e52.13 1000.204GB eth2 8704 up,kickme > e52.14 1000.204GB eth2 8704 up,kickme > e52.15 1000.204GB eth2 8704 up,kickme > e52.16 1000.204GB eth2 8704 up,kickme > e52.17 1000.204GB eth2 8704 up,kickme > e52.18 1000.204GB eth2 8704 up,kickme > e52.19 1000.204GB eth2 8704 up,kickme > e52.20 1000.204GB eth2 8704 up,kickme > e52.2 1000.204GB eth2 8704 up,kickme > e52.21 1000.204GB eth2 8704 up,kickme > e52.22 1000.204GB eth2 8704 up,kickme > e52.23 1000.204GB eth2 8704 up,kickme > e52.3 1000.204GB eth2 8704 up,kickme > e52.4 1000.204GB eth2 8704 up,kickme > e52.5 1000.204GB eth2 8704 up,kickme > e52.6 1000.204GB eth2 8704 up,kickme > e52.7 1000.204GB eth2 8704 up,kickme > e52.8 1000.204GB eth2 8704 up,kickme > e52.9 1000.204GB eth2 8704 up,kickme > > > Daofeng > > On Tue, Jun 16, 2015 at 8:23 PM, Ed Cashin <ed....@ac...> wrote: > >> (I mean aoe-sancheck, with a hyphen.) >> >> >> On 06/16/2015 08:39 PM, Ed Cashin wrote: >> >> Adi, do you think aoetools-36/aoesancheck is a good next step? >> >> On 06/16/2015 01:57 PM, Daofeng Li wrote: >> >> ok...I'm totally lost... :) >> >> $ ethtool -k em1 >> Features for em1: >> rx-checksumming: on >> tx-checksumming: on >> tx-checksum-ipv4: on >> tx-checksum-ip-generic: off [fixed] >> tx-checksum-ipv6: on >> tx-checksum-fcoe-crc: on [fixed] >> tx-checksum-sctp: on >> scatter-gather: on >> tx-scatter-gather: on >> tx-scatter-gather-fraglist: off [fixed] >> tcp-segmentation-offload: on >> tx-tcp-segmentation: on >> tx-tcp-ecn-segmentation: off [fixed] >> tx-tcp6-segmentation: on >> udp-fragmentation-offload: off [fixed] >> generic-segmentation-offload: on >> generic-receive-offload: on >> large-receive-offload: on >> rx-vlan-offload: on >> tx-vlan-offload: on >> ntuple-filters: off >> receive-hashing: on >> highdma: on [fixed] >> rx-vlan-filter: on >> vlan-challenged: off [fixed] >> tx-lockless: off [fixed] >> netns-local: off [fixed] >> tx-gso-robust: off [fixed] >> tx-fcoe-segmentation: on [fixed] >> tx-gre-segmentation: off [fixed] >> tx-ipip-segmentation: off [fixed] >> tx-sit-segmentation: off [fixed] >> tx-udp_tnl-segmentation: off [fixed] >> tx-mpls-segmentation: off [fixed] >> fcoe-mtu: off [fixed] >> tx-nocache-copy: on >> loopback: off [fixed] >> rx-fcs: off [fixed] >> rx-all: off >> tx-vlan-stag-hw-insert: off [fixed] >> rx-vlan-stag-hw-parse: off [fixed] >> rx-vlan-stag-filter: off [fixed] >> l2-fwd-offload: off >> >> >> Daofeng >> >> On Tue, Jun 16, 2015 at 12:55 PM, Daofeng Li <li...@gm...> wrote: >> >>> Thanks Adi, I'll try. >>> >>> best, >>> >>> >>> Daofeng >>> >>> On Tue, Jun 16, 2015 at 12:01 PM, Adi Kriegisch <ad...@cg...> >>> wrote: >>> >>>> Hey! >>>> >>>> > Honestly..I don't know what those dropped packets, it;s just a new >>>> > installed system. >>>> I see... depending on what services are running on that network, this >>>> might >>>> be some avahi messages or similar stuff; in case this is a storage-only >>>> network and there is no other stuff floating around, this may well be >>>> the >>>> cause for the issues... >>>> >>>> > Do you mean my MTU 9000 is too high? >>>> No, I don't think so. Maybe some of the ethernet offloading stuff in the >>>> NIC is unable to handle larger packets? You may check with 'ethtool -k >>>> em1' >>>> what is enabled and may try to selectively disable and retest... >>>> >>>> -- Adi >>>> >>> >>> >> >> >> ------------------------------------------------------------------------------ >> >> >> >> _______________________________________________ >> Aoetools-discuss mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/aoetools-discuss >> >> >> >> >> ------------------------------------------------------------------------------ >> >> >> >> _______________________________________________ >> Aoetools-discuss mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/aoetools-discuss >> >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Aoetools-discuss mailing list >> Aoe...@li... >> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss >> >> > |
