Discussion:
[Aoetools-discuss] end_request: I/O error
Daofeng Li
2015-06-16 16:12:18 UTC
Permalink
Dear list,

I was trying to relocating my storage from 1 server to another, the old one
has aoe driver version 81 installed, the new has 85 installed, I see this
error message on the new system only. Is there a way to fix them? Thanks a
lot.

Jun 15 17:11:01 cluster kernel: [ 1243.965424] end_request: I/O error,
dev etherd/e50.23, sector 1953523728
Jun 15 17:11:01 cluster kernel: [ 1243.965436] aoe: device 52.23 is not up
Jun 15 17:11:01 cluster kernel: [ 1243.965440] end_request: I/O error,
dev etherd/e52.23, sector 1953524240
Jun 15 17:11:01 cluster kernel: [ 1243.965443] aoe: device 52.23 is not up
Jun 15 17:11:01 cluster kernel: [ 1243.965445] end_request: I/O error,
dev etherd/e52.23, sector 528
Jun 15 17:11:01 cluster kernel: [ 1243.965447] aoe: device 52.23 is not up
Jun 15 17:11:01 cluster kernel: [ 1243.965449] aoe: device 52.23 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.126390] aoe: device 50.23 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.126395] end_request: I/O error,
dev etherd/e50.23, sector 1953524240
Jun 15 17:11:01 cluster kernel: [ 1244.177397] aoe: device 50.23 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.177401] end_request: I/O error,
dev etherd/e50.23, sector 528
Jun 15 17:11:01 cluster kernel: [ 1244.226678] aoe: device 50.23 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.226681] aoe: device 50.23 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.226697] end_request: I/O error,
dev etherd/e52.22, sector 1953523728
Jun 15 17:11:01 cluster kernel: [ 1244.274831] aoe: device 52.22 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.274834] end_request: I/O error,
dev etherd/e52.22, sector 1953524240
Jun 15 17:11:01 cluster kernel: [ 1244.321528] aoe: device 52.22 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.321531] end_request: I/O error,
dev etherd/e52.22, sector 528
Jun 15 17:11:01 cluster kernel: [ 1244.366733] aoe: device 52.22 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.366736] aoe: device 52.22 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.366760] end_request: I/O error,
dev etherd/e50.22, sector 1953523728
Jun 15 17:11:01 cluster kernel: [ 1244.410629] aoe: device 50.22 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.410633] end_request: I/O error,
dev etherd/e50.22, sector 1953524240
Jun 15 17:11:01 cluster kernel: [ 1244.453077] aoe: device 50.22 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453082] aoe: device 50.22 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453084] aoe: device 50.22 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453100] aoe: device 52.21 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453104] aoe: device 52.21 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453107] aoe: device 52.21 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453109] aoe: device 52.21 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453116] aoe: device 50.21 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453121] aoe: device 50.21 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453125] aoe: device 50.21 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453127] aoe: device 50.21 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453133] aoe: device 52.20 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453145] aoe: device 52.20 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453156] aoe: device 52.20 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453163] aoe: device 52.20 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453190] aoe: device 50.20 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453200] aoe: device 50.20 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453219] aoe: device 50.20 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453222] aoe: device 50.20 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453230] aoe: device 52.19 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453235] aoe: device 52.19 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453239] aoe: device 52.19 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453241] aoe: device 52.19 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453249] aoe: device 52.18 is not up
Jun 15 17:11:01 cluster kernel: [ 1244.453260] aoe: device 52.18 is not up


y aoe-stat command actually told the system could found the disks:

# aoe-stat
e50.0 1000.204GB em1 8704 up
e50.10 1000.204GB em1 8704 up
e50.1 1000.204GB em1 8704 up
e50.11 1000.204GB em1 8704 up
e50.12 1000.204GB em1 8704 up
e50.13 1000.204GB em1 8704 up
e50.14 1000.204GB em1 8704 up
e50.15 1000.204GB em1 8704 up
e50.16 1000.204GB em1 8704 up
e50.17 1000.204GB em1 8704 up
e50.18 1000.204GB em1 8704 up
e50.19 1000.204GB em1 8704 up
e50.20 1000.204GB em1 8704 up
e50.2 1000.204GB em1 8704 up
e50.21 1000.204GB em1 8704 up
e50.22 1000.204GB em1 8704 up
e50.23 1000.204GB em1 8704 up
e50.3 1000.204GB em1 8704 up
e50.4 1000.204GB em1 8704 up
e50.5 1000.204GB em1 8704 up
e50.6 1000.204GB em1 8704 up
e50.7 1000.204GB em1 8704 up
e50.8 1000.204GB em1 8704 up
e50.9 1000.204GB em1 8704 up
e52.0 1000.204GB em1 8704 up
e52.10 1000.204GB em1 8704 up
e52.1 1000.204GB em1 8704 up
e52.11 1000.204GB em1 8704 up
e52.12 1000.204GB em1 8704 up
e52.13 1000.204GB em1 8704 up
e52.14 1000.204GB em1 8704 up
e52.15 1000.204GB em1 8704 up
e52.16 1000.204GB em1 8704 up
e52.17 1000.204GB em1 8704 up
e52.18 1000.204GB em1 8704 up
e52.19 1000.204GB em1 8704 up
e52.20 1000.204GB em1 8704 up
e52.2 1000.204GB em1 8704 up
e52.21 1000.204GB em1 8704 up
e52.22 1000.204GB em1 8704 up
e52.23 1000.204GB em1 8704 up
e52.3 1000.204GB em1 8704 up
e52.4 1000.204GB em1 8704 up
e52.5 1000.204GB em1 8704 up
e52.6 1000.204GB em1 8704 up
e52.7 1000.204GB em1 8704 up
e52.8 1000.204GB em1 8704 up
e52.9 1000.204GB em1 8704 up

network, system and driver information:


***@cluster:/home/d# ifconfig

em1 Link encap:Ethernet HWaddr 5c:f9:dd:b9:48:a8

inet addr:10.200.0.20 Bcast:10.200.0.255 Mask:255.255.255.0

inet6 addr: fe80::5ef9:ddff:feb9:48a8/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1

RX packets:392548 errors:0 dropped:337 overruns:0 frame:0

TX packets:311526 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:164961826 (164.9 MB) TX bytes:20663984 (20.6 MB)


lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:1325 errors:0 dropped:0 overruns:0 frame:0

TX packets:1325 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:23850 (23.8 KB) TX bytes:23850 (23.8 KB)


***@cluster:/home/d# uname -a

Linux cluster 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux

***@cluster:/home/d# aoe-version

aoetools: 36

installed aoe driver: 85

running aoe driver: 85


Daofeng
Daofeng Li
2015-06-16 16:54:36 UTC
Permalink
Hi Adi,

Thanks for your reply.
Honestly..I don't know what those dropped packets, it;s just a new
installed system.
Do you mean my MTU 9000 is too high?

Daofeng
Post by Daofeng Li
Hey!
Post by Daofeng Li
I was trying to relocating my storage from 1 server to another, the
old
Post by Daofeng Li
one has aoe driver version 81 installed, the new has 85 installed, I
see
Post by Daofeng Li
this error message on the new system only. Is there a way to fix them?
[...]
Post by Daofeng Li
Jun 15 17:11:01 cluster kernel: [ 1243.965424] end_request: I/O error,
dev etherd/e50.23, sector 1953523728
[...]
Post by Daofeng Li
# aoe-stat
e50.23 1000.204GB em1 8704 up
[...]
Post by Daofeng Li
em1 Link encap:Ethernet HWaddr 5c:f9:dd:b9:48:a8
inet addr:10.200.0.20 Bcast:10.200.0.255
Mask:255.255.255.0
Post by Daofeng Li
inet6 addr: fe80::5ef9:ddff:feb9:48a8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:392548 errors:0 dropped:337 overruns:0 frame:0
TX packets:311526 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:164961826 (164.9 MB) TX bytes:20663984 (20.6 MB)
Strange. Do you have any idea what the dropped packets (337 above) are?
Other than that, are there any offloading features (ethtool) enabled on the
nic that cannot reliably deal with jumbo frames?
-- Adi
Daofeng Li
2015-06-16 16:56:28 UTC
Permalink
Some output from dmesg:

[67285.437643] systemd-udevd[7632]: starting version 204
[68228.934696] aoe: AoE v85 initialised.
[68228.935045] aoe: e52.23: setting 8704 byte data frames
[68228.935073] aoe: e50.23: setting 8704 byte data frames
[68228.935081] aoe: e52.22: setting 8704 byte data frames
[68228.935098] aoe: e50.22: setting 8704 byte data frames
[68228.935104] aoe: e52.21: setting 8704 byte data frames
[68228.935110] aoe: e50.21: setting 8704 byte data frames
[68228.935121] aoe: e52.20: setting 8704 byte data frames
[68228.935133] aoe: e50.20: setting 8704 byte data frames
[68228.935146] aoe: e52.19: setting 8704 byte data frames
[68228.935152] aoe: e50.19: setting 8704 byte data frames
[68228.935163] aoe: e52.18: setting 8704 byte data frames
[68228.935169] aoe: e52.17: setting 8704 byte data frames
[68228.935180] aoe: e50.18: setting 8704 byte data frames
[68228.935188] aoe: e52.16: setting 8704 byte data frames
[68228.935197] aoe: e50.17: setting 8704 byte data frames
[68228.935203] aoe: e52.15: setting 8704 byte data frames
[68228.935212] aoe: e50.16: setting 8704 byte data frames
[68228.935220] aoe: e52.14: setting 8704 byte data frames
[68228.935227] aoe: e50.15: setting 8704 byte data frames
[68228.935233] aoe: e52.13: setting 8704 byte data frames
[68228.935242] aoe: e50.14: setting 8704 byte data frames
[68228.935250] aoe: e52.12: setting 8704 byte data frames
[68228.935258] aoe: e50.13: setting 8704 byte data frames
[68228.935265] aoe: e52.11: setting 8704 byte data frames
[68228.935274] aoe: e50.12: setting 8704 byte data frames
[68228.935281] aoe: e52.10: setting 8704 byte data frames
[68228.935290] aoe: e50.11: setting 8704 byte data frames
[68228.935297] aoe: e52.9: setting 8704 byte data frames
[68228.935306] aoe: e52.8: setting 8704 byte data frames
[68228.935316] aoe: e50.10: setting 8704 byte data frames
[68228.935323] aoe: e52.7: setting 8704 byte data frames
[68228.935330] aoe: e50.9: setting 8704 byte data frames
[68228.935347] aoe: e52.6: setting 8704 byte data frames
[68228.935356] aoe: e50.8: setting 8704 byte data frames
[68228.935365] aoe: e52.5: setting 8704 byte data frames
[68228.935373] aoe: e50.7: setting 8704 byte data frames
[68228.935380] aoe: e52.4: setting 8704 byte data frames
[68228.935389] aoe: e50.6: setting 8704 byte data frames
[68228.935395] aoe: e52.3: setting 8704 byte data frames
[68228.935404] aoe: e50.5: setting 8704 byte data frames
[68228.935413] aoe: e52.2: setting 8704 byte data frames
[68228.935423] aoe: e50.4: setting 8704 byte data frames
[68228.935433] aoe: e52.1: setting 8704 byte data frames
[68228.935443] aoe: e50.3: setting 8704 byte data frames
[68228.935451] aoe: e52.0: setting 8704 byte data frames
[68228.935458] aoe: e50.2: setting 8704 byte data frames
[68228.935467] aoe: e50.1: setting 8704 byte data frames
[68228.935475] aoe: e50.0: setting 8704 byte data frames
[68228.935505] aoe: 00259005ba18 e50.23 vace0 has 1953525117 sectors
[68228.935861] aoe: 00259005ba18 e50.22 vace0 has 1953525117 sectors
[68228.936182] aoe: 00259005ba18 e50.21 vace0 has 1953525117 sectors
[68228.936477] aoe: 00259005ba18 e50.20 vace0 has 1953525117 sectors
[68228.936720] aoe: 00259005ba18 e50.19 vace0 has 1953525117 sectors
[68228.937132] aoe: 00259005ba18 e50.18 vace0 has 1953525117 sectors
[68228.937316] etherd/e50.23: unknown partition table
[68228.937524] aoe: 00259005ba18 e50.17 vace0 has 1953525117 sectors
[68228.937600] aoe: 00259005ba18 e50.16 vace0 has 1953525117 sectors
[68228.937698] aoe: 00259005ba18 e50.15 vace0 has 1953525117 sectors
[68228.937704] etherd/e50.22: unknown partition table
[68228.938019] aoe: 00259005ba18 e50.14 vace0 has 1953525117 sectors
[68228.938114] etherd/e50.21: unknown partition table
[68228.938372] aoe: 00259005ba18 e50.13 vace0 has 1953525117 sectors
[68228.938693] aoe: 00259005ba18 e50.12 vace0 has 1953525117 sectors
[68228.938703] etherd/e50.20: unknown partition table
[68228.938903] etherd/e50.19: unknown partition table
[68228.939022] aoe: 00259005ba18 e50.11 vace0 has 1953525117 sectors
[68228.939167] etherd/e50.18: unknown partition table
[68228.939447] aoe: 00259005ba18 e50.10 vace0 has 1953525117 sectors
[68228.939510] etherd/e50.17: unknown partition table
[68228.939731] etherd/e50.16: unknown partition table
[68228.939913] etherd/e50.15: unknown partition table
[68228.940178] etherd/e50.14: unknown partition table
[68228.940386] aoe: 003048dd4d24 e52.23 vace0 has 1953525117 sectors
[68228.940394] aoe: 003048dd4d24 e52.22 vace0 has 1953525117 sectors
[68228.940399] aoe: 003048dd4d24 e52.21 vace0 has 1953525117 sectors
[68228.940404] aoe: 003048dd4d24 e52.20 vace0 has 1953525117 sectors
[68228.940408] aoe: 003048dd4d24 e52.19 vace0 has 1953525117 sectors
[68228.940413] aoe: 003048dd4d24 e52.18 vace0 has 1953525117 sectors
[68228.940418] aoe: 003048dd4d24 e52.17 vace0 has 1953525117 sectors
[68228.940423] aoe: 003048dd4d24 e52.16 vace0 has 1953525117 sectors
[68228.940427] aoe: 003048dd4d24 e52.15 vace0 has 1953525117 sectors
[68228.940432] aoe: 003048dd4d24 e52.14 vace0 has 1953525117 sectors
[68228.940437] aoe: 003048dd4d24 e52.13 vace0 has 1953525117 sectors
[68228.940442] aoe: 003048dd4d24 e52.12 vace0 has 1953525117 sectors
[68228.940447] aoe: 003048dd4d24 e52.11 vace0 has 1953525117 sectors
[68228.940451] aoe: 003048dd4d24 e52.10 vace0 has 1953525117 sectors
[68228.940456] aoe: 003048dd4d24 e52.9 vace0 has 1953525117 sectors
[68228.940705] etherd/e50.13: unknown partition table
[68228.940829] etherd/e50.12: unknown partition table
[68228.941300] etherd/e50.11: unknown partition table
[68228.941471] etherd/e50.10: unknown partition table
[68228.941688] aoe: 003048dd4d24 e52.8 vace0 has 1953525117 sectors
[68228.942115] aoe: 003048dd4d24 e52.7 vace0 has 1953525117 sectors
[68228.942265] etherd/e52.23: unknown partition table
[68228.942484] etherd/e52.22: unknown partition table
[68228.943372] etherd/e52.21: unknown partition table
[68228.943552] etherd/e52.20: unknown partition table
[68228.943646] aoe: 003048dd4d24 e52.6 vace0 has 1953525117 sectors
[68228.943947] aoe: 003048dd4d24 e52.5 vace0 has 1953525117 sectors
[68228.944205] aoe: 003048dd4d24 e52.4 vace0 has 1953525117 sectors
[68228.944289] aoe: 003048dd4d24 e52.3 vace0 has 1953525117 sectors
[68228.944662] etherd/e52.8: unknown partition table
[68228.944922] aoe: 003048dd4d24 e52.2 vace0 has 1953525117 sectors
[68228.945204] aoe: 003048dd4d24 e52.1 vace0 has 1953525117 sectors
[68228.945541] aoe: 003048dd4d24 e52.0 vace0 has 1953525117 sectors
[68228.945554] aoe: 00259005ba18 e50.9 vace0 has 1953525117 sectors
[68228.945564] aoe: 00259005ba18 e50.8 vace0 has 1953525117 sectors
[68228.945574] aoe: 00259005ba18 e50.7 vace0 has 1953525117 sectors
[68228.945582] aoe: 00259005ba18 e50.6 vace0 has 1953525117 sectors
[68228.945588] aoe: 00259005ba18 e50.5 vace0 has 1953525117 sectors
[68228.945593] aoe: 00259005ba18 e50.4 vace0 has 1953525117 sectors
[68228.945598] aoe: 00259005ba18 e50.3 vace0 has 1953525117 sectors
[68228.945603] aoe: 00259005ba18 e50.2 vace0 has 1953525117 sectors
[68228.945609] aoe: 00259005ba18 e50.1 vace0 has 1953525117 sectors
[68228.945615] aoe: 00259005ba18 e50.0 vace0 has 1953525117 sectors
[68228.945681] etherd/e52.17: unknown partition table
[68228.946105] etherd/e52.19: unknown partition table
[68228.946944] etherd/e52.18: unknown partition table
[68228.947842] etherd/e52.5: unknown partition table
[68228.948044] etherd/e52.6: unknown partition table
[68228.948251] etherd/e52.16: unknown partition table
[68228.948501] etherd/e52.15: unknown partition table
[68228.948850] etherd/e52.4: unknown partition table
[68228.948951] etherd/e52.7: unknown partition table
[68228.949169] etherd/e52.3: unknown partition table
[68228.949365] etherd/e52.14: unknown partition table
[68228.949811] etherd/e52.2: unknown partition table
[68228.950151] etherd/e50.9: unknown partition table
[68228.950244] etherd/e52.13: unknown partition table
[68228.950303] etherd/e52.1: unknown partition table
[68228.950451] etherd/e52.11: unknown partition table
[68228.950476] etherd/e52.0: unknown partition table
[68228.950714] etherd/e52.12: unknown partition table
[68228.950923] etherd/e50.8: unknown partition table
[68228.950964] etherd/e52.10: unknown partition table
[68228.951785] etherd/e52.9: unknown partition table
[68228.952319] etherd/e50.7: unknown partition table
[68228.953696] etherd/e50.5: unknown partition table
[68228.954214] etherd/e50.6: unknown partition table
[68228.954685] etherd/e50.4: unknown partition table
[68228.955174] etherd/e50.3: unknown partition table
[68228.955687] etherd/e50.1: unknown partition table
[68228.955902] etherd/e50.2: unknown partition table
[68228.956829] etherd/e50.0: unknown partition table

​But I do have this error, haven't found a solution by google yet:

# aoe-discover
aoe-discover: /dev/etherd/discover does not exist or is not writeable.​


Daofeng
Post by Daofeng Li
Hi Adi,
Thanks for your reply.
Honestly..I don't know what those dropped packets, it;s just a new
installed system.
Do you mean my MTU 9000 is too high?
Daofeng
Post by Daofeng Li
Hey!
Post by Daofeng Li
I was trying to relocating my storage from 1 server to another, the
old
Post by Daofeng Li
one has aoe driver version 81 installed, the new has 85 installed, I
see
Post by Daofeng Li
this error message on the new system only. Is there a way to fix
them?
[...]
Post by Daofeng Li
Jun 15 17:11:01 cluster kernel: [ 1243.965424] end_request: I/O error,
dev etherd/e50.23, sector 1953523728
[...]
Post by Daofeng Li
# aoe-stat
e50.23 1000.204GB em1 8704 up
[...]
Post by Daofeng Li
em1 Link encap:Ethernet HWaddr 5c:f9:dd:b9:48:a8
inet addr:10.200.0.20 Bcast:10.200.0.255
Mask:255.255.255.0
Post by Daofeng Li
inet6 addr: fe80::5ef9:ddff:feb9:48a8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
RX packets:392548 errors:0 dropped:337 overruns:0 frame:0
TX packets:311526 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:164961826 (164.9 MB) TX bytes:20663984 (20.6 MB)
Strange. Do you have any idea what the dropped packets (337 above) are?
Other than that, are there any offloading features (ethtool) enabled on the
nic that cannot reliably deal with jumbo frames?
-- Adi
Adi Kriegisch
2015-06-16 17:01:27 UTC
Permalink
Hey!
Post by Daofeng Li
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...
Post by Daofeng Li
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

------------------------------------------------------------------------------
Daofeng Li
2015-06-16 17:55:00 UTC
Permalink
Thanks Adi, I'll try.

​best,​


Daofeng
Post by Adi Kriegisch
Hey!
Post by Daofeng Li
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...
Post by Daofeng Li
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
Daofeng Li
2015-06-16 17:57:26 UTC
Permalink
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
Post by Daofeng Li
Thanks Adi, I'll try.
​best,​
Daofeng
Post by Adi Kriegisch
Hey!
Post by Daofeng Li
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...
Post by Daofeng Li
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
Ed Cashin
2015-06-17 00:39:54 UTC
Permalink
Adi, do you think aoetools-36/aoesancheck is a good next step?
Post by Daofeng Li
ok...I'm totally lost... :)
$ ethtool -k 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
Thanks Adi, I'll try.
​best,​
Daofeng
On Tue, Jun 16, 2015 at 12:01 PM, Adi Kriegisch
Hey!
Post by Daofeng Li
Honestly..I don't know what those dropped packets, it;s
just a new
Post by Daofeng Li
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...
Post by Daofeng Li
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 list
https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
Ed Cashin
2015-06-17 01:23:58 UTC
Permalink
(I mean aoe-sancheck, with a hyphen.)
Post by Ed Cashin
Adi, do you think aoetools-36/aoesancheck is a good next step?
Post by Daofeng Li
ok...I'm totally lost... :)
$ ethtool -k 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
Thanks Adi, I'll try.
​best,​
Daofeng
On Tue, Jun 16, 2015 at 12:01 PM, Adi Kriegisch
Hey!
Post by Daofeng Li
Honestly..I don't know what those dropped packets, it;s
just a new
Post by Daofeng Li
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...
Post by Daofeng Li
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 list
https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
------------------------------------------------------------------------------
_______________________________________________
Aoetools-discuss mailing list
https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
Daofeng Li
2015-06-17 05:07:34 UTC
Permalink
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
Post by Ed Cashin
(I mean aoe-sancheck, with a hyphen.)
Adi, do you think aoetools-36/aoesancheck is a good next step?
ok...I'm totally lost... :)
$ ethtool -k 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
Post by Daofeng Li
Thanks Adi, I'll try.
​best,​
Daofeng
Post by Adi Kriegisch
Hey!
Post by Daofeng Li
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...
Post by Daofeng Li
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 list
https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
Daofeng Li
2015-06-17 05:11:11 UTC
Permalink
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
Post by Daofeng Li
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
Post by Ed Cashin
(I mean aoe-sancheck, with a hyphen.)
Adi, do you think aoetools-36/aoesancheck is a good next step?
ok...I'm totally lost... :)
$ ethtool -k 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
Post by Daofeng Li
Thanks Adi, I'll try.
​best,​
Daofeng
Post by Adi Kriegisch
Hey!
Post by Daofeng Li
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...
Post by Daofeng Li
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 list
https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
Adi Kriegisch
2015-06-17 20:09:10 UTC
Permalink
Hi!
Post by Daofeng Li
Probably my MTU is too high? Thanks again.
I actually don't think so. A MTU of 9000 is quite common and the Dell
interface (em1) you showed us is quite capable.

@Ed: Excellent hint to use aoe-sancheck! I completely missed that...
Post by Daofeng Li
# aoe-sancheck
[...]
Post by Daofeng Li
eth2    UP      9000    14e4:164f
[...]
Post by Daofeng Li
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
[[...]
Post by Daofeng Li
$ ethtool -k em1
[...]
I just ask myself, why aoe-sancheck finds your aoe storage via eth2 (which
should then be em3?) and not via em1. Did you change something on your
setup?

-- Adi

------------------------------------------------------------------------------
Loading...