[DRBD-user] Tracking down sources of corruption (possibly) detected by drbdadm verify...

Admin drbd-info at internode.com.au
Tue Jan 15 23:59:17 CET 2008

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On Wed, 16 Jan 2008 02:40:46 am Florian Haas wrote:
> Hello Mysterious Stranger (I assume "Admin" is not your first name),
>
> Why don't we first try and see if your network stack is eating data.
>
> Do something like this:
>
> host1:~ # dd if=/dev/urandom of=/tmp/foobar bs=1M count=256
> host1:~ # md5sum /tmp/foobar
>
> host2:~ # netcat -l -p 4711 | md5sum
>
> host1:~ # netcat -q0 192.168.2.2 4711 < /tmp/foobar
>
> ... and let us know if those two MD5 sums match. Just in case, before we
> dive deeper into this.
>
> Cheers,
> Florian

host1:~ # ethtool -k eth3
Offload parameters for eth3:
Cannot get device udp large send offload settings: Operation not supported
rx-checksumming: off
tx-checksumming: off
scatter-gather: off
tcp segmentation offload: off
udp fragmentation offload: off
generic segmentation offload: off
host1:~ # dd if=/dev/urandom of=/tmp/foobar bs=1M count=256
host1:~ # md5sum /tmp/foobar
5eaf46836f635a41ddae4c74aba24712  /tmp/foobar

host2:~ # ethtool -k eth3
Offload parameters for eth3:
Cannot get device udp large send offload settings: Operation not supported
rx-checksumming: off
tx-checksumming: off
scatter-gather: off
tcp segmentation offload: off
udp fragmentation offload: off
generic segmentation offload: off
host2:~ # nc -l -p 4711 | md5sum

host1:~ # nc -q0 192.168.2.2 4711 < /tmp/foobar

Host2:~ 
5eaf46836f635a41ddae4c74aba24712  -

md5s match, so no corruption is apparent with that test.

Interestingly, ethtool can no longer enable TSO on the forcedeth interface of 
either node.

host1 ~ #  ethtool -K eth3 tso on 
Cannot set device tcp segmentation offload settings: Invalid argument

host2 ~ # ethtool -K eth3 tso on 
Cannot set device tcp segmentation offload settings: Invalid argument

These boxes have 2 broadcom BCM5715 (rev a3) interfaces in addition to the 
forcedeth ones. Ethtool is still able to enable and disable tso on those 
interfaces.

Here's the output of ifconfig (mtu 1500 for eth3) for each host

host1 ~ # ifconfig eth3
eth3      Link encap:Ethernet  HWaddr 00:16:36:8E:13:27  
          inet addr:192.168.2.1  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::216:36ff:fe8e:1327/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:157591853 errors:0 dropped:0 overruns:0 frame:0
          TX packets:271122834 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:22926667464 (21864.5 Mb)  TX bytes:571243020428 (544779.7 
Mb)
          Interrupt:248 Base address:0x6000 

host2 ~ # ifconfig eth3
eth3      Link encap:Ethernet  HWaddr 00:16:36:D7:56:9D  
          inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::216:36ff:fed7:569d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:397412152 errors:0 dropped:0 overruns:0 frame:0
          TX packets:157514475 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:569653361264 (543263.7 Mb)  TX bytes:23557033656 (22465.7 
Mb)
          Interrupt:249 Base address:0x6000 


M.S.



More information about the drbd-user mailing list