Re: Data corruption over NFS in -current

2012-01-19 Thread Rick Macklem
Martin Cracauer wrote: > More findings. > > Reminder, with the original report I found: > - files for no reason changing ownership and group to > root/ > - data corruption as in inserting binary junk obviously from ports > - data corruption as in malformed ascii text that might be a bug I > have i

Re: Data corruption over NFS in -current

2012-01-16 Thread Ivan Voras
On 13/01/2012 15:37, Martin Cracauer wrote: More findings. Reminder, with the original report I found: - files for no reason changing ownership and group to root/ - data corruption as in inserting binary junk obviously from ports - data corruption as in malformed ascii text that might be a bu

Re: Data corruption over NFS in -current

2012-01-13 Thread Rick Macklem
Martin Cracauer wrote: > More findings. > > Reminder, with the original report I found: > - files for no reason changing ownership and group to > root/ > - data corruption as in inserting binary junk obviously from ports > - data corruption as in malformed ascii text that might be a bug I > have i

Re: Data corruption over NFS in -current

2012-01-13 Thread Martin Cracauer
More findings. Reminder, with the original report I found: - files for no reason changing ownership and group to root/ - data corruption as in inserting binary junk obviously from ports - data corruption as in malformed ascii text that might be a bug I have in my code that is only exposed in F

Re: Data corruption over NFS in -current

2012-01-12 Thread Daniel Braniss
> > --+QahgC5+KEYLbs62 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > Stefan Bethke wrote on Wed, Jan 11, 2012 at 07:14:44PM +0100: > > Am 11.01.2012 um 17:57 schrieb Martin Cracauer: > > > > > I'm sorry for the unspecific bug report but I thought a heads-up is >

Re: Data corruption over NFS in -current

2012-01-11 Thread Dan Nelson
In the last episode (Jan 11), Martin Cracauer said: > Rick Macklem wrote on Wed, Jan 11, 2012 at 08:42:25PM -0500: > > Also, if you can reproduce the problem fairly easily, capture a packet > > trace via > > # tcpdump -s 0 -w xxx host > > running on the client (or similar). Then email me "xxx" a

Re: Data corruption over NFS in -current

2012-01-11 Thread Martin Cracauer
Rick Macklem wrote on Wed, Jan 11, 2012 at 08:42:25PM -0500: > Martin Cracauer wrote: > > Stefan Bethke wrote on Wed, Jan 11, 2012 at 07:14:44PM +0100: > > > Am 11.01.2012 um 17:57 schrieb Martin Cracauer: > > > > > > > I'm sorry for the unspecific bug report but I thought a heads-up > > > > is >

Re: Data corruption over NFS in -current

2012-01-11 Thread Rick Macklem
Martin Cracauer wrote: > Stefan Bethke wrote on Wed, Jan 11, 2012 at 07:14:44PM +0100: > > Am 11.01.2012 um 17:57 schrieb Martin Cracauer: > > > > > I'm sorry for the unspecific bug report but I thought a heads-up > > > is > > > better than none. > > > > > > $ uname -a > > > FreeBSD wings.cons.org

Re: Data corruption over NFS in -current

2012-01-11 Thread Martin Cracauer
Stefan Bethke wrote on Wed, Jan 11, 2012 at 07:14:44PM +0100: > Am 11.01.2012 um 17:57 schrieb Martin Cracauer: > > > I'm sorry for the unspecific bug report but I thought a heads-up is > > better than none. > > > > $ uname -a > > FreeBSD wings.cons.org 10.0-CURRENT FreeBSD 10.0-CURRENT #2: Wed

Re: Data corruption over NFS in -current

2012-01-11 Thread Stefan Bethke
Am 11.01.2012 um 17:57 schrieb Martin Cracauer: > I'm sorry for the unspecific bug report but I thought a heads-up is > better than none. > > $ uname -a > FreeBSD wings.cons.org 10.0-CURRENT FreeBSD 10.0-CURRENT #2: Wed Dec > 28 12:19:21 EST 2011 > craca...@wings.cons.org:/usr/src/sys/amd64/compi