than flaky hardware.
Thanks for your help to those who took the time to reply.
Martin.
From: Martin Minkus
Sent: Monday, 28 June 2010 09:22
To: freebsd-questions@freebsd.org
Subject: RE: sshd / tcp packet corruption ? ZFS Samba?
Hey all,
It was suggested I do a memtest
Hey all,
It was suggested I do a memtest, but that checked out fine. (I wish it
was as simple as just the ram!)
I’ve realised the issue manifests itself almost immediately when
accessing an underlying ZFS filesystem using Samba. But if it is UFS, it
is fine.
Does this mean anything to
Martin Minkus martin.min...@punz.co.nz writes:
It seems this issue I reported below may actually be related to some
kind of TCP packet corruption ?
Possible. Or memory errors. Hard to say much at this point, when you
don't even know which side is actually causing the errors.
Still same
point. I'll do a memtest.
Martin.
-Original Message-
From: Lowell Gilbert [mailto:freebsd-questions-lo...@be-well.ilk.org]
Sent: Thursday, 24 June 2010 09:41
To: Martin Minkus
Cc: freebsd-questions
Subject: Re: sshd / tcp packet corruption ?
Martin Minkus martin.min...@punz.co.nz writes
So definitely some kind of packet corruption;
Using netcat to send a single megabyte of binary data to a box with no
known issues (from kinetic - steel):
kinetic:/tmp$ dd if=/dev/urandom of=random.testfile bs=1k count=1k
1024+0 records in
1024+0 records out
1048576 bytes transferred in