Mikolaj Golub (to.my.trociny) writes:
>
> Ok. So it is send(2). I suppose the network driver could generate the
> error. Did you tell what network adaptor you had?
Not yet.
bce0: <HP NC382i DP Multifunction Gigabit Server Adapter (C0)> mem
0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci2
bce0: ASIC (0x57092003); Rev (C0); Bus (PCIe x2, 2.5Gbps); B/C (4.6.4);
Bufs (RX:2;TX:2;PG:8); Flags (SPLT|MSI|MFW); MFW (NCSI 1.0.3)
> PR> No obvious errors there either, but again what should I look out for
> ?
>
> I would look at sysctl -a dev.<nic> statistics and try to find if there is
> correlation
> between ENOMEM failures and growing of error counters.
0 errors:
dev.bce.0.l2fhdr_error_count: 0
dev.bce.0.stat_emac_tx_stat_dot3statsinternalmactransmiterrors: 0
dev.bce.0.stat_Dot3StatsCarrierSenseErrors: 0
dev.bce.0.stat_Dot3StatsFCSErrors: 0
dev.bce.0.stat_Dot3StatsAlignmentErrors: 0
> Looking at buffer usage from 'netstat -nax' output ran during synchronization
> (on both hosts) could provide useful info where the bottleneck is. top -HS
> output might be useful too.
Good point.
I'll have to attempt to recreate the problem, as the volume has
replicated
without errors. Typical.
Cheers,
Phil
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
