aoetools-discuss Mailing List for ATA over Ethernet Tools (Page 3)
Brought to you by:
ecashin,
elcapitansam
Menu
▾
▴
aoetools-discuss — General discussion list for AoE and aoetools
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
(3) |
Mar
(14) |
Apr
(24) |
May
|
Jun
(8) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
(16) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(21) |
Feb
(7) |
Mar
(6) |
Apr
(10) |
May
(16) |
Jun
(17) |
Jul
(28) |
Aug
(50) |
Sep
(72) |
Oct
(44) |
Nov
(41) |
Dec
(33) |
| 2007 |
Jan
(10) |
Feb
(35) |
Mar
(29) |
Apr
(17) |
May
(5) |
Jun
(9) |
Jul
(12) |
Aug
(23) |
Sep
(27) |
Oct
(7) |
Nov
(15) |
Dec
(2) |
| 2008 |
Jan
(12) |
Feb
(25) |
Mar
(31) |
Apr
(30) |
May
(21) |
Jun
(16) |
Jul
(24) |
Aug
(2) |
Sep
(26) |
Oct
(15) |
Nov
(4) |
Dec
(12) |
| 2009 |
Jan
(7) |
Feb
(34) |
Mar
(38) |
Apr
(41) |
May
(37) |
Jun
|
Jul
(16) |
Aug
(7) |
Sep
(10) |
Oct
(15) |
Nov
(22) |
Dec
(7) |
| 2010 |
Jan
(9) |
Feb
(1) |
Mar
(3) |
Apr
(15) |
May
(23) |
Jun
(9) |
Jul
(1) |
Aug
(4) |
Sep
(2) |
Oct
(14) |
Nov
(9) |
Dec
(3) |
| 2011 |
Jan
|
Feb
(8) |
Mar
(6) |
Apr
(5) |
May
(10) |
Jun
(6) |
Jul
(48) |
Aug
(8) |
Sep
(15) |
Oct
|
Nov
(6) |
Dec
(6) |
| 2012 |
Jan
(1) |
Feb
(2) |
Mar
(12) |
Apr
(27) |
May
(15) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(10) |
Nov
(6) |
Dec
|
| 2013 |
Jan
(2) |
Feb
(1) |
Mar
(11) |
Apr
(12) |
May
(8) |
Jun
(1) |
Jul
(3) |
Aug
|
Sep
(10) |
Oct
(17) |
Nov
|
Dec
|
| 2014 |
Jan
(6) |
Feb
|
Mar
(6) |
Apr
(1) |
May
(39) |
Jun
(20) |
Jul
(10) |
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2015 |
Jan
|
Feb
(8) |
Mar
|
Apr
(1) |
May
(3) |
Jun
(16) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(3) |
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
(9) |
| 2017 |
Jan
(4) |
Feb
|
Mar
(3) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
(9) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(5) |
Oct
(5) |
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Keri A. <k.a...@sy...> - 2015-07-08 15:21:56
|
Sorry about this off-topic post. We are trying to contact Sam Hopkins. Anyone have a recent and functional email address for him? Let's not post his contact info on the list...just indicate that you have an address and we will take this offline. Thanks. |
|
From: Adi K. <ad...@cg...> - 2015-06-17 20:09:20
|
Hi! > 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... > # aoe-sancheck [...] > eth2 UP 9000 14e4:164f [...] > 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 [[...] > $ ethtool -k em1 > Features for 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 |
|
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 >> >> > |
|
From: Daofeng Li <li...@gm...> - 2015-06-17 05:08:01
|
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
>
>
|
|
From: Ed C. <ed....@ac...> - 2015-06-17 01:52:10
|
Hi. There's a new aoetools release. Please try it and provide feedback if you can. https://github.com/OpenAoE/aoetools/archive/aoetools-37.tar.gz Here is a snippet from the NEWS file: 2015-06-16 Ed Cashin <ed....@ac...> update documentation for OpenAoE clean up code based on set-not-used compiler warnings release 37 -- Ed |
|
From: Ed C. <ed....@ac...> - 2015-06-17 01:24:11
|
(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... >> <mailto:li...@gm...>> wrote: >> >> Thanks Adi, I'll try. >> >> best, >> >> >> Daofeng >> >> On Tue, Jun 16, 2015 at 12:01 PM, Adi Kriegisch >> <ad...@cg... <mailto: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 list >> Aoe...@li... >> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Aoetools-discuss mailing list > Aoe...@li... > https://lists.sourceforge.net/lists/listinfo/aoetools-discuss |
|
From: Ed C. <ed....@ac...> - 2015-06-17 01:06:46
|
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... > <mailto:li...@gm...>> wrote: > > Thanks Adi, I'll try. > > best, > > > Daofeng > > On Tue, Jun 16, 2015 at 12:01 PM, Adi Kriegisch > <ad...@cg... <mailto: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 list > Aoe...@li... > https://lists.sourceforge.net/lists/listinfo/aoetools-discuss |
|
From: Daofeng Li <li...@gm...> - 2015-06-16 17:57:53
|
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 >> > > |
|
From: Daofeng Li <li...@gm...> - 2015-06-16 17:55:27
|
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 > |
|
From: Adi K. <ad...@cg...> - 2015-06-16 17:32:19
|
Hey! > 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? [...] > Jun 15 17:11:01 cluster kernel: [ 1243.965424] end_request: I/O error, dev etherd/e50.23, sector 1953523728 [...] > # aoe-stat > e50.23 1000.204GB em1 8704 up [...] > root@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) 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 |
|
From: Adi K. <ad...@cg...> - 2015-06-16 17:32:11
|
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 |
|
From: Daofeng Li <li...@gm...> - 2015-06-16 16:56:56
|
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 On Tue, Jun 16, 2015 at 11:54 AM, Daofeng Li <li...@gm...> wrote: > 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 > > On Tue, Jun 16, 2015 at 11:52 AM, Adi Kriegisch <ad...@cg...> > wrote: > >> Hey! >> >> > 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? >> [...] >> > Jun 15 17:11:01 cluster kernel: [ 1243.965424] end_request: I/O error, >> dev etherd/e50.23, sector 1953523728 >> [...] >> > # aoe-stat >> > e50.23 1000.204GB em1 8704 up >> [...] >> > root@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) >> 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 >> > > |
|
From: Daofeng Li <li...@gm...> - 2015-06-16 16:55:03
|
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 On Tue, Jun 16, 2015 at 11:52 AM, Adi Kriegisch <ad...@cg...> wrote: > Hey! > > > 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? > [...] > > Jun 15 17:11:01 cluster kernel: [ 1243.965424] end_request: I/O error, > dev etherd/e50.23, sector 1953523728 > [...] > > # aoe-stat > > e50.23 1000.204GB em1 8704 up > [...] > > root@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) > 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 > |
|
From: Daofeng Li <li...@gm...> - 2015-06-16 16:12:45
|
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:
root@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)
root@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
root@cluster:/home/d# aoe-version
aoetools: 36
installed aoe driver: 85
running aoe driver: 85
Daofeng
|
|
From: Ed C. <ed....@ac...> - 2015-06-15 01:10:51
|
The vblade-23 release is out with minor updates. https://github.com/OpenAoE/vblade/releases/tag/vblade-23 On 06/12/2015 09:48 PM, Ed Cashin wrote: > Hi. > > There is some stuff going on, but some of it is on github and openaoe.org. > > I'm also working on updating the aoetools RPM to support > systemd-oriented RPM macros. > > https://github.com/OpenAoE/ > http://www.openaoe.org/ > > Does the pre-release aoe driver (aoe6-86pre1) work for you, if you can > try it? > > https://github.com/OpenAoE/aoe/releases > > On 06/11/2015 01:09 PM, Pongrácz István wrote: >> >> just a test, I did not receive emails for a looooong time >> >> Bye, >> >> Steve >> >> >> >> ------------------------------------------------------------------------------ >> >> >> _______________________________________________ >> Aoetools-discuss mailing list >> Aoe...@li... >> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Aoetools-discuss mailing list > Aoe...@li... > https://lists.sourceforge.net/lists/listinfo/aoetools-discuss |
|
From: Ed C. <ed....@ac...> - 2015-06-13 02:15:43
|
Hi. There is some stuff going on, but some of it is on github and openaoe.org. I'm also working on updating the aoetools RPM to support systemd-oriented RPM macros. https://github.com/OpenAoE/ http://www.openaoe.org/ Does the pre-release aoe driver (aoe6-86pre1) work for you, if you can try it? https://github.com/OpenAoE/aoe/releases On 06/11/2015 01:09 PM, Pongrácz István wrote: > > just a test, I did not receive emails for a looooong time > > Bye, > > Steve > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Aoetools-discuss mailing list > Aoe...@li... > https://lists.sourceforge.net/lists/listinfo/aoetools-discuss |
|
From: Pongrácz I. <pon...@gm...> - 2015-06-11 17:09:16
|
just a test, I did not receive emails for a looooong time Bye, Steve |
|
From: Ed C. <ed....@ac...> - 2015-05-26 18:44:38
|
Coraid had a reduced support team last I heard. Have you contacted Coraid support? You can sometimes use aoeping from the aoetools to find out which targets are accessible. Normal configuration problems include failure to enable jumbo frames and failure to bring the interfaces up on the Linux hosts. (I can't really debug your situation now, but those are a couple things to check.) On May 25, 2015 11:35 PM, Daofeng Li <li...@gm...> wrote: > > Dear list members, > > I am using Ubuntu 12.04 with aoetools 81 for my Coraid box. > I used to use a 10Gb switch with CX-4 cable to connect the Coraid. > Somehow my switch failed and I had to use the Ethernet port with Rj45 cable. > But my issue is that only some of my disks show up when I use aoe-stat, I tried reboot both server and Coraid for few time but without lucky. > my shelf could be accessed through eth0 using cec command. > > Did anyone have some suggestions? Thanks a lot in advance. > > root@server1:~# uname -a > Linux server1 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux > root@server1:~# aoe-version > aoetools: 34 > installed aoe driver: 81 > : 81 > running aoe driver: 81 > > > root@corona:~# cec eth0 > Probing for shelves ... done. > SHELF | EA > 50 00259005BA18 > 51 002590053BF8 > 52 003048DD4D24 > [#qp]: 50 > connecting ... done. > Escape is Ctrl-\ > > SRX shelf 50> disks > DISK SIZE MODEL FIRMWARE MODE > 50.0 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.1 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.2 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.3 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.4 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.5 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.6 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.7 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.8 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.9 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.10 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.11 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.12 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.13 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.14 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.15 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.16 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.17 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.18 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.19 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.20 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.21 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.22 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > 50.23 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s > SRX shelf 50> list > 0 1000.205GB online > 1 1000.205GB online > 2 1000.205GB online > 3 1000.205GB online > 4 1000.205GB online > 5 1000.205GB online > 6 1000.205GB online > 7 1000.205GB online > 8 1000.205GB online > 9 1000.205GB online > 10 1000.205GB online > 11 1000.205GB online > 12 1000.205GB online > 13 1000.205GB online > 14 1000.205GB online > 15 1000.205GB online > 16 1000.205GB online > 17 1000.205GB online > 18 1000.205GB online > 19 1000.205GB online > 20 1000.205GB online > 21 1000.205GB online > 22 1000.205GB online > 23 1000.205GB online > SRX shelf 50> >>> > (q)uit, (i)nterrupt, (.)continue > >>> q > SHELF | EA > 50 00259005BA18 > 51 002590053BF8 > 52 003048DD4D24 > [#qp]: root@server1:~# > root@server1:~# aoe-discover > root@server1:~# aoe-stat > e51.14 2000.398GB eth0 1024 up > e51.16 2000.398GB eth0 1024 up > e51.17 2000.398GB eth0 1024 up > e51.19 2000.398GB eth0 1024 up > e51.20 2000.398GB eth0 1024 up > e51.2 2000.398GB eth0 1024 up > e51.22 2000.398GB eth0 1024 up > e51.23 2000.398GB eth0 1024 up > e51.4 2000.398GB eth0 1024 up > e51.6 2000.398GB eth0 1024 up > e51.8 2000.398GB eth0 1024 up > > > Daofeng |
|
From: Daofeng Li <li...@gm...> - 2015-05-26 18:19:18
|
Thank you for your info, Ed :) Best, Daofeng On Tue, May 26, 2015 at 1:17 PM, Ed Cashin <ed....@ac...> wrote: > Coraid had a reduced support team last I heard. Have you contacted Coraid > support? > > You can sometimes use aoeping from the aoetools to find out which targets > are accessible. > > Normal configuration problems include failure to enable jumbo frames and > failure to bring the interfaces up on the Linux hosts. (I can't really > debug your situation now, but those are a couple things to check.) > > On May 25, 2015 11:35 PM, Daofeng Li <li...@gm...> wrote: > > > > Dear list members, > > > > I am using Ubuntu 12.04 with aoetools 81 for my Coraid box. > > I used to use a 10Gb switch with CX-4 cable to connect the Coraid. > > Somehow my switch failed and I had to use the Ethernet port with Rj45 > cable. > > But my issue is that only some of my disks show up when I use aoe-stat, > I tried reboot both server and Coraid for few time but without lucky. > > my shelf could be accessed through eth0 using cec command. > > > > Did anyone have some suggestions? Thanks a lot in advance. > > > > root@server1:~# uname -a > > Linux server1 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC > 2012 x86_64 x86_64 x86_64 GNU/Linux > > root@server1:~# aoe-version > > aoetools: 34 > > installed aoe driver: 81 > > : 81 > > running aoe driver: 81 > > > > > > root@corona:~# cec eth0 > > Probing for shelves ... done. > > SHELF | EA > > 50 00259005BA18 > > 51 002590053BF8 > > 52 003048DD4D24 > > [#qp]: 50 > > connecting ... done. > > Escape is Ctrl-\ > > > > SRX shelf 50> disks > > DISK SIZE MODEL FIRMWARE > MODE > > 50.0 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.1 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.2 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.3 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.4 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.5 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.6 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.7 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.8 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.9 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.10 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.11 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.12 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.13 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.14 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.15 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.16 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.17 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.18 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.19 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.20 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.21 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.22 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > 50.23 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata > 3.0Gb/s > > SRX shelf 50> list > > 0 1000.205GB online > > 1 1000.205GB online > > 2 1000.205GB online > > 3 1000.205GB online > > 4 1000.205GB online > > 5 1000.205GB online > > 6 1000.205GB online > > 7 1000.205GB online > > 8 1000.205GB online > > 9 1000.205GB online > > 10 1000.205GB online > > 11 1000.205GB online > > 12 1000.205GB online > > 13 1000.205GB online > > 14 1000.205GB online > > 15 1000.205GB online > > 16 1000.205GB online > > 17 1000.205GB online > > 18 1000.205GB online > > 19 1000.205GB online > > 20 1000.205GB online > > 21 1000.205GB online > > 22 1000.205GB online > > 23 1000.205GB online > > SRX shelf 50> >>> > > (q)uit, (i)nterrupt, (.)continue > > >>> q > > SHELF | EA > > 50 00259005BA18 > > 51 002590053BF8 > > 52 003048DD4D24 > > [#qp]: root@server1:~# > > root@server1:~# aoe-discover > > root@server1:~# aoe-stat > > e51.14 2000.398GB eth0 1024 up > > e51.16 2000.398GB eth0 1024 up > > e51.17 2000.398GB eth0 1024 up > > e51.19 2000.398GB eth0 1024 up > > e51.20 2000.398GB eth0 1024 up > > e51.2 2000.398GB eth0 1024 up > > e51.22 2000.398GB eth0 1024 up > > e51.23 2000.398GB eth0 1024 up > > e51.4 2000.398GB eth0 1024 up > > e51.6 2000.398GB eth0 1024 up > > e51.8 2000.398GB eth0 1024 up > > > > > > Daofeng > |
|
From: Daofeng Li <li...@gm...> - 2015-05-26 03:36:22
|
Dear list members,
I am using Ubuntu 12.04 with aoetools 81 for my Coraid box.
I used to use a 10Gb switch with CX-4 cable to connect the Coraid.
Somehow my switch failed and I had to use the Ethernet port with Rj45 cable.
But my issue is that only some of my disks show up when I use aoe-stat, I
tried reboot both server and Coraid for few time but without lucky.
my shelf could be accessed through eth0 using cec command.
Did anyone have some suggestions? Thanks a lot in advance.
root@server1:~# uname -a
Linux server1 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
root@server1:~# aoe-version
aoetools: 34
installed aoe driver: 81
: 81
running aoe driver: 81
root@corona:~# cec eth0
Probing for shelves ... done.
SHELF | EA
50 00259005BA18
51 002590053BF8
52 003048DD4D24
[#qp]: 50
connecting ... done.
Escape is Ctrl-\
SRX shelf 50> disks
DISK SIZE MODEL FIRMWARE MODE
50.0 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.1 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.2 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.3 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.4 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.5 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.6 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.7 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.8 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.9 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.10 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.11 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.12 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.13 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.14 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.15 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.16 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.17 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.18 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.19 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.20 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.21 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.22 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
50.23 1000.204GB WDC WD1002FBYS-02A6B0 03.00C06 sata 3.0Gb/s
SRX shelf 50> list
0 1000.205GB online
1 1000.205GB online
2 1000.205GB online
3 1000.205GB online
4 1000.205GB online
5 1000.205GB online
6 1000.205GB online
7 1000.205GB online
8 1000.205GB online
9 1000.205GB online
10 1000.205GB online
11 1000.205GB online
12 1000.205GB online
13 1000.205GB online
14 1000.205GB online
15 1000.205GB online
16 1000.205GB online
17 1000.205GB online
18 1000.205GB online
19 1000.205GB online
20 1000.205GB online
21 1000.205GB online
22 1000.205GB online
23 1000.205GB online
SRX shelf 50> >>>
(q)uit, (i)nterrupt, (.)continue
>>> q
SHELF | EA
50 00259005BA18
51 002590053BF8
52 003048DD4D24
[#qp]: root@server1:~#
root@server1:~# aoe-discover
root@server1:~# aoe-stat
e51.14 2000.398GB eth0 1024 up
e51.16 2000.398GB eth0 1024 up
e51.17 2000.398GB eth0 1024 up
e51.19 2000.398GB eth0 1024 up
e51.20 2000.398GB eth0 1024 up
e51.2 2000.398GB eth0 1024 up
e51.22 2000.398GB eth0 1024 up
e51.23 2000.398GB eth0 1024 up
e51.4 2000.398GB eth0 1024 up
e51.6 2000.398GB eth0 1024 up
e51.8 2000.398GB eth0 1024 up
Daofeng
|
|
From: Ed C. <ed....@ac...> - 2015-04-14 01:58:20
|
Hi. This prerelease, https://github.com/OpenAoE/aoe/releases/tag/aoe6-86pre1 ... at the new github project for OpenAoE, http://www.openaoe.org/ ... is compile-tested to be compatible with new kernels. It has backward compatibility with older kernels. The changes are significant but are intended to closely mirror upstream changes in the upstream kernel's built-in aoe driver. As usual, they're accompanied by backwards-compatibility tests and patches that allow the driver to work on older kernels as well. Please try out this prerelease and let me or the list know how it works. -- Ed |
|
From: Catalin S. <cs...@us...> - 2015-02-26 10:36:26
|
Not specifically related to the patch. I believe you should, maybe, change the HACKING document(and maybe rename it or merge it to README. not everybody seams to like that term nowadays) and include instructions on providing patches against the GitHub repo. I'm also of the opinion that you should merge head into 'staging' or close the 'staging' branch after every release and believe rc tags should be on staging or separate branches. I wanted to issue the pull request against that, but it was out of date with master so I had less of a choice. On 26/02/2015 4:56 AM, Ed Cashin wrote: > Great! After merging, I made a pre-release: > > https://github.com/ecashin/vblade/releases/tag/v23-rc1 > > On 02/25/2015 07:50 AM, Catalin Salgau wrote: >> As requested, I've opened a pull request for this. >> I have not included the full explanation in the man page as I believe >> that is for initiators to work on, not targets. >> I'm open to further changes. >> Thanks! >> >> On 21/02/2015 3:45 AM, Ed Cashin wrote: >>> These days, when something appears not to be working, people Google. >>> >>> So we've already done a lot by putting information that they can find on >>> the mailing list. >>> >>> The original email was almost exactly what someone would need to find >>> when they Google: A succinct, well founded, specific explanation of the >>> danger and what can be done to avoid it. If that explanation is in the >>> vblade documentation, it will be even easier to find with a web search. >>> >>> And really, that's what the documentation is for. The fact that people >>> don't read documentation isn't a good reason to make noisy tools. Then >>> they'll ignore the noise just like they ignore the documentation. ;) >>> >>> If nobody really has time to do a pull request with a documentation >>> update based on the contents of the original email, I'll do it in a >>> week. >>> >>> On 02/19/2015 08:10 AM, Catalin Salgau wrote: >>>> I tend to be of the same opinion, with the added note that I knew >>>> about the alignment differences prior to debugging this and we still >>>> fell for it. I doubt that a warning in a man page would come to mind >>>> (or really match what one would be looking for) when a user notices >>>> corruption issues in running systems. >>>> A log warning also has the added benefit that it can provide a >>>> straight-forward value to truncate against. >>>> @Ed: I'm not rigid regarding this and it's your call; however, I lack >>>> the time to provide pull requests for any of these at the moment, and >>>> the code I provided wasn't tested (we currently apply that correction >>>> externally, but it's essentially the same and it's not hard to follow) >>>> >>>> >>>> On 19/02/2015 6:39 AM, Joshua J. Kugler wrote: >>>>> You might argue that people are more likely to read the logs than the >>>>> docs...but then, a lot of people read neither until something goes >>>>> wrong. But >>>>> maybe finding that message in the logs is more likely to happen when >>>>> something >>>>> goes wrong, rather than "Hmm, something is wrong, I think I'll go >>>>> look for >>>>> warnings in the docs." >>>>> >>>>> But maybe that's just me. :) >>>>> >>>>> j >>>>> >>>>> On Wednesday, February 18, 2015 22:51:47 Ed Cashin wrote: >>>>>> Would you consider a pull request that includes an addition to the >>>>> documentation? That seems like a more appropriate place for a >>>>> warning. On Feb >>>>> 18, 2015 10:01 PM, Catalin Salgau <cs...@us...> >>>>> wrote: >>>>>>> Hi. >>>>>>> >>>>>>> While I haven't gotten around to testing any of the "recent" >>>>>>> changes, a >>>>>>> colleague finally tracked down one of our long-standing corruption >>>>>>> issues some time ago and I think I should suggest a change that >>>>>>> might >>>>>>> help others. >>>>>>> WinAoE has some code in the GettingsSize state that truncates a >>>>>>> disk to >>>>>>> CHS geometry. Prior to Vista, Windows enforced CHS alignment for >>>>>>> partition boundaries, so this was not a problem. >>>>>>> However, if you installed a newer OS (one using 1MB boundaries) then >>>>>>> moved it to AoE storage, truncating at a partition boundary could >>>>>>> cause >>>>>>> sectors to be missing under WinAoE, corrupting your data. Windows >>>>>>> probably never actually relied on this behaviour, since it was >>>>>>> enforcing >>>>>>> alignment itself. >>>>>>> >>>>>>> I would like to request a warning along the lines of (while the 512 >>>>>>> byte >>>>>>> sector size is superfluous, I include it for clarity) >>>>>>> #define CHSALIGN 255*63*512 >>>>>>> if ((size*512) % CHSALIGN) { >>>>>>> vlong recsz = (size*512) + CHSALIGN - (size*512)%CHSALIGN; >>>>>>> printf("Exported size (%llu) is not aligned to usual CHS >>>>>>> geometry.\n", size*512) >>>>>>> printf("Consider truncating to %llu bytes to prevent >>>>>>> issues.\n", >>>>>>> recsz); } >>>>>>> Please excuse the lack of a pull request. >>>>>>> I'll try getting back to the other changes I was proposing at a >>>>>>> later >>>>>>> time. >>>>>>> Thanks! >>>>>>> >>>>>>> -------------------------------------------------------------------------- >>>>>>> >>>>>>> >>>>>>> ---- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT >>>>>>> Server >>>>>>> from Actuate! Instantly Supercharge Your Business Reports and >>>>>>> Dashboards >>>>>>> with Interactivity, Sharing, Native Excel Exports, App Integration >>>>>>> & more >>>>>>> Get technology previously reserved for billion-dollar corporations, >>>>>>> FREE >>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clkt >>>>>>> >>>>>>> >>>>>>> rk _______________________________________________ >>>>>>> Aoetools-discuss mailing list >>>>>>> Aoe...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss >>>>>> >>>>>> ---------------------------------------------------------------------------- >>>>>> >>>>>> >>>>>> -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >>>>>> from Actuate! Instantly Supercharge Your Business Reports and >>>>>> Dashboards >>>>>> with Interactivity, Sharing, Native Excel Exports, App Integration & >>>>>> more >>>>>> Get technology previously reserved for billion-dollar corporations, >>>>>> FREE >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Aoetools-discuss mailing list >>>>>> Aoe...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss >>>>> >>> >>> > > |
|
From: Ed C. <ed....@ac...> - 2015-02-26 03:23:20
|
Great! After merging, I made a pre-release: https://github.com/ecashin/vblade/releases/tag/v23-rc1 On 02/25/2015 07:50 AM, Catalin Salgau wrote: > As requested, I've opened a pull request for this. > I have not included the full explanation in the man page as I believe > that is for initiators to work on, not targets. > I'm open to further changes. > Thanks! > > On 21/02/2015 3:45 AM, Ed Cashin wrote: >> These days, when something appears not to be working, people Google. >> >> So we've already done a lot by putting information that they can find on >> the mailing list. >> >> The original email was almost exactly what someone would need to find >> when they Google: A succinct, well founded, specific explanation of the >> danger and what can be done to avoid it. If that explanation is in the >> vblade documentation, it will be even easier to find with a web search. >> >> And really, that's what the documentation is for. The fact that people >> don't read documentation isn't a good reason to make noisy tools. Then >> they'll ignore the noise just like they ignore the documentation. ;) >> >> If nobody really has time to do a pull request with a documentation >> update based on the contents of the original email, I'll do it in a >> week. >> >> On 02/19/2015 08:10 AM, Catalin Salgau wrote: >>> I tend to be of the same opinion, with the added note that I knew >>> about the alignment differences prior to debugging this and we still >>> fell for it. I doubt that a warning in a man page would come to mind >>> (or really match what one would be looking for) when a user notices >>> corruption issues in running systems. >>> A log warning also has the added benefit that it can provide a >>> straight-forward value to truncate against. >>> @Ed: I'm not rigid regarding this and it's your call; however, I lack >>> the time to provide pull requests for any of these at the moment, and >>> the code I provided wasn't tested (we currently apply that correction >>> externally, but it's essentially the same and it's not hard to follow) >>> >>> >>> On 19/02/2015 6:39 AM, Joshua J. Kugler wrote: >>>> You might argue that people are more likely to read the logs than the >>>> docs...but then, a lot of people read neither until something goes >>>> wrong. But >>>> maybe finding that message in the logs is more likely to happen when >>>> something >>>> goes wrong, rather than "Hmm, something is wrong, I think I'll go >>>> look for >>>> warnings in the docs." >>>> >>>> But maybe that's just me. :) >>>> >>>> j >>>> >>>> On Wednesday, February 18, 2015 22:51:47 Ed Cashin wrote: >>>>> Would you consider a pull request that includes an addition to the >>>> documentation? That seems like a more appropriate place for a >>>> warning. On Feb >>>> 18, 2015 10:01 PM, Catalin Salgau <cs...@us...> >>>> wrote: >>>>>> Hi. >>>>>> >>>>>> While I haven't gotten around to testing any of the "recent" >>>>>> changes, a >>>>>> colleague finally tracked down one of our long-standing corruption >>>>>> issues some time ago and I think I should suggest a change that >>>>>> might >>>>>> help others. >>>>>> WinAoE has some code in the GettingsSize state that truncates a >>>>>> disk to >>>>>> CHS geometry. Prior to Vista, Windows enforced CHS alignment for >>>>>> partition boundaries, so this was not a problem. >>>>>> However, if you installed a newer OS (one using 1MB boundaries) then >>>>>> moved it to AoE storage, truncating at a partition boundary could >>>>>> cause >>>>>> sectors to be missing under WinAoE, corrupting your data. Windows >>>>>> probably never actually relied on this behaviour, since it was >>>>>> enforcing >>>>>> alignment itself. >>>>>> >>>>>> I would like to request a warning along the lines of (while the 512 >>>>>> byte >>>>>> sector size is superfluous, I include it for clarity) >>>>>> #define CHSALIGN 255*63*512 >>>>>> if ((size*512) % CHSALIGN) { >>>>>> vlong recsz = (size*512) + CHSALIGN - (size*512)%CHSALIGN; >>>>>> printf("Exported size (%llu) is not aligned to usual CHS >>>>>> geometry.\n", size*512) >>>>>> printf("Consider truncating to %llu bytes to prevent >>>>>> issues.\n", >>>>>> recsz); } >>>>>> Please excuse the lack of a pull request. >>>>>> I'll try getting back to the other changes I was proposing at a >>>>>> later >>>>>> time. >>>>>> Thanks! >>>>>> >>>>>> -------------------------------------------------------------------------- >>>>>> >>>>>> >>>>>> ---- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT >>>>>> Server >>>>>> from Actuate! Instantly Supercharge Your Business Reports and >>>>>> Dashboards >>>>>> with Interactivity, Sharing, Native Excel Exports, App Integration >>>>>> & more >>>>>> Get technology previously reserved for billion-dollar corporations, >>>>>> FREE >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clkt >>>>>> >>>>>> >>>>>> rk _______________________________________________ >>>>>> Aoetools-discuss mailing list >>>>>> Aoe...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss >>>>> >>>>> ---------------------------------------------------------------------------- >>>>> >>>>> >>>>> -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >>>>> from Actuate! Instantly Supercharge Your Business Reports and >>>>> Dashboards >>>>> with Interactivity, Sharing, Native Excel Exports, App Integration & >>>>> more >>>>> Get technology previously reserved for billion-dollar corporations, >>>>> FREE >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk >>>>> >>>>> >>>>> _______________________________________________ >>>>> Aoetools-discuss mailing list >>>>> Aoe...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss >>>> >> >> |
|
From: Catalin S. <cs...@us...> - 2015-02-25 12:50:25
|
As requested, I've opened a pull request for this.
I have not included the full explanation in the man page as I believe
that is for initiators to work on, not targets.
I'm open to further changes.
Thanks!
On 21/02/2015 3:45 AM, Ed Cashin wrote:
> These days, when something appears not to be working, people Google.
>
> So we've already done a lot by putting information that they can find on
> the mailing list.
>
> The original email was almost exactly what someone would need to find
> when they Google: A succinct, well founded, specific explanation of the
> danger and what can be done to avoid it. If that explanation is in the
> vblade documentation, it will be even easier to find with a web search.
>
> And really, that's what the documentation is for. The fact that people
> don't read documentation isn't a good reason to make noisy tools. Then
> they'll ignore the noise just like they ignore the documentation. ;)
>
> If nobody really has time to do a pull request with a documentation
> update based on the contents of the original email, I'll do it in a week.
>
> On 02/19/2015 08:10 AM, Catalin Salgau wrote:
>> I tend to be of the same opinion, with the added note that I knew
>> about the alignment differences prior to debugging this and we still
>> fell for it. I doubt that a warning in a man page would come to mind
>> (or really match what one would be looking for) when a user notices
>> corruption issues in running systems.
>> A log warning also has the added benefit that it can provide a
>> straight-forward value to truncate against.
>> @Ed: I'm not rigid regarding this and it's your call; however, I lack
>> the time to provide pull requests for any of these at the moment, and
>> the code I provided wasn't tested (we currently apply that correction
>> externally, but it's essentially the same and it's not hard to follow)
>>
>>
>> On 19/02/2015 6:39 AM, Joshua J. Kugler wrote:
>>> You might argue that people are more likely to read the logs than the
>>> docs...but then, a lot of people read neither until something goes
>>> wrong. But
>>> maybe finding that message in the logs is more likely to happen when
>>> something
>>> goes wrong, rather than "Hmm, something is wrong, I think I'll go
>>> look for
>>> warnings in the docs."
>>>
>>> But maybe that's just me. :)
>>>
>>> j
>>>
>>> On Wednesday, February 18, 2015 22:51:47 Ed Cashin wrote:
>>>> Would you consider a pull request that includes an addition to the
>>> documentation? That seems like a more appropriate place for a
>>> warning. On Feb
>>> 18, 2015 10:01 PM, Catalin Salgau <cs...@us...> wrote:
>>>>> Hi.
>>>>>
>>>>> While I haven't gotten around to testing any of the "recent"
>>>>> changes, a
>>>>> colleague finally tracked down one of our long-standing corruption
>>>>> issues some time ago and I think I should suggest a change that might
>>>>> help others.
>>>>> WinAoE has some code in the GettingsSize state that truncates a
>>>>> disk to
>>>>> CHS geometry. Prior to Vista, Windows enforced CHS alignment for
>>>>> partition boundaries, so this was not a problem.
>>>>> However, if you installed a newer OS (one using 1MB boundaries) then
>>>>> moved it to AoE storage, truncating at a partition boundary could
>>>>> cause
>>>>> sectors to be missing under WinAoE, corrupting your data. Windows
>>>>> probably never actually relied on this behaviour, since it was
>>>>> enforcing
>>>>> alignment itself.
>>>>>
>>>>> I would like to request a warning along the lines of (while the 512
>>>>> byte
>>>>> sector size is superfluous, I include it for clarity)
>>>>> #define CHSALIGN 255*63*512
>>>>> if ((size*512) % CHSALIGN) {
>>>>> vlong recsz = (size*512) + CHSALIGN - (size*512)%CHSALIGN;
>>>>> printf("Exported size (%llu) is not aligned to usual CHS
>>>>> geometry.\n", size*512)
>>>>> printf("Consider truncating to %llu bytes to prevent issues.\n",
>>>>> recsz); }
>>>>> Please excuse the lack of a pull request.
>>>>> I'll try getting back to the other changes I was proposing at a later
>>>>> time.
>>>>> Thanks!
>>>>>
>>>>> --------------------------------------------------------------------------
>>>>>
>>>>> ---- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>>>> from Actuate! Instantly Supercharge Your Business Reports and
>>>>> Dashboards
>>>>> with Interactivity, Sharing, Native Excel Exports, App Integration
>>>>> & more
>>>>> Get technology previously reserved for billion-dollar corporations,
>>>>> FREE
>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clkt
>>>>>
>>>>> rk _______________________________________________
>>>>> Aoetools-discuss mailing list
>>>>> Aoe...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
>>>>
>>>> ----------------------------------------------------------------------------
>>>>
>>>> -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>>> from Actuate! Instantly Supercharge Your Business Reports and
>>>> Dashboards
>>>> with Interactivity, Sharing, Native Excel Exports, App Integration &
>>>> more
>>>> Get technology previously reserved for billion-dollar corporations,
>>>> FREE
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>>>>
>>>> _______________________________________________
>>>> Aoetools-discuss mailing list
>>>> Aoe...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
>>>
>
>
|
|
From: Ed C. <ed....@ac...> - 2015-02-21 02:12:01
|
These days, when something appears not to be working, people Google.
So we've already done a lot by putting information that they can find on
the mailing list.
The original email was almost exactly what someone would need to find
when they Google: A succinct, well founded, specific explanation of the
danger and what can be done to avoid it. If that explanation is in the
vblade documentation, it will be even easier to find with a web search.
And really, that's what the documentation is for. The fact that people
don't read documentation isn't a good reason to make noisy tools. Then
they'll ignore the noise just like they ignore the documentation. ;)
If nobody really has time to do a pull request with a documentation
update based on the contents of the original email, I'll do it in a week.
On 02/19/2015 08:10 AM, Catalin Salgau wrote:
> I tend to be of the same opinion, with the added note that I knew
> about the alignment differences prior to debugging this and we still
> fell for it. I doubt that a warning in a man page would come to mind
> (or really match what one would be looking for) when a user notices
> corruption issues in running systems.
> A log warning also has the added benefit that it can provide a
> straight-forward value to truncate against.
> @Ed: I'm not rigid regarding this and it's your call; however, I lack
> the time to provide pull requests for any of these at the moment, and
> the code I provided wasn't tested (we currently apply that correction
> externally, but it's essentially the same and it's not hard to follow)
>
>
> On 19/02/2015 6:39 AM, Joshua J. Kugler wrote:
>> You might argue that people are more likely to read the logs than the
>> docs...but then, a lot of people read neither until something goes
>> wrong. But
>> maybe finding that message in the logs is more likely to happen when
>> something
>> goes wrong, rather than "Hmm, something is wrong, I think I'll go
>> look for
>> warnings in the docs."
>>
>> But maybe that's just me. :)
>>
>> j
>>
>> On Wednesday, February 18, 2015 22:51:47 Ed Cashin wrote:
>>> Would you consider a pull request that includes an addition to the
>> documentation? That seems like a more appropriate place for a
>> warning. On Feb
>> 18, 2015 10:01 PM, Catalin Salgau <cs...@us...> wrote:
>>>> Hi.
>>>>
>>>> While I haven't gotten around to testing any of the "recent"
>>>> changes, a
>>>> colleague finally tracked down one of our long-standing corruption
>>>> issues some time ago and I think I should suggest a change that might
>>>> help others.
>>>> WinAoE has some code in the GettingsSize state that truncates a
>>>> disk to
>>>> CHS geometry. Prior to Vista, Windows enforced CHS alignment for
>>>> partition boundaries, so this was not a problem.
>>>> However, if you installed a newer OS (one using 1MB boundaries) then
>>>> moved it to AoE storage, truncating at a partition boundary could
>>>> cause
>>>> sectors to be missing under WinAoE, corrupting your data. Windows
>>>> probably never actually relied on this behaviour, since it was
>>>> enforcing
>>>> alignment itself.
>>>>
>>>> I would like to request a warning along the lines of (while the 512
>>>> byte
>>>> sector size is superfluous, I include it for clarity)
>>>> #define CHSALIGN 255*63*512
>>>> if ((size*512) % CHSALIGN) {
>>>> vlong recsz = (size*512) + CHSALIGN - (size*512)%CHSALIGN;
>>>> printf("Exported size (%llu) is not aligned to usual CHS
>>>> geometry.\n", size*512)
>>>> printf("Consider truncating to %llu bytes to prevent issues.\n",
>>>> recsz); }
>>>> Please excuse the lack of a pull request.
>>>> I'll try getting back to the other changes I was proposing at a later
>>>> time.
>>>> Thanks!
>>>>
>>>> --------------------------------------------------------------------------
>>>>
>>>> ---- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>>> from Actuate! Instantly Supercharge Your Business Reports and
>>>> Dashboards
>>>> with Interactivity, Sharing, Native Excel Exports, App Integration
>>>> & more
>>>> Get technology previously reserved for billion-dollar corporations,
>>>> FREE
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clkt
>>>>
>>>> rk _______________________________________________
>>>> Aoetools-discuss mailing list
>>>> Aoe...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
>>>
>>> ----------------------------------------------------------------------------
>>>
>>> -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>> from Actuate! Instantly Supercharge Your Business Reports and
>>> Dashboards
>>> with Interactivity, Sharing, Native Excel Exports, App Integration &
>>> more
>>> Get technology previously reserved for billion-dollar corporations,
>>> FREE
>>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>>>
>>> _______________________________________________
>>> Aoetools-discuss mailing list
>>> Aoe...@li...
>>> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
>>
|
29 messages has been excluded from this view by a project administrator.
