Date: Mon, 16 Jan 2012 17:35:34 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Data corruption over NFS in -current Message-ID: <jf1jkn$un8$1@dough.gmane.org> In-Reply-To: <20120113143711.GA62486@cons.org> References: <20120111165714.GA46594@cons.org> <E9C4060A-0BD5-4187-BE1D-F46560C64366@lassitu.de> <20120111182110.GA75991@cons.org> <E1RlFsD-000OQB-Cr@kabab.cs.huji.ac.il> <20120113143711.GA62486@cons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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/<owngroupname> > - 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 FreeBSD > I re-ran with newfs (reboot) which worked (all three problems absent). > > I then started building ports/land/gcc47 at the same time as I > re-started my crazy script and it too only a few seconds for an > unexpected ownership to root to occur. Two more things to check: 1) Are you using tmpfs? Could you try without it? 2) Are you really sure your hardware is ok? If everything works fine after a reboot, it might mean that there is a memory corruption and you don't use that specific memory until some time after the reboot. Try running memtest86.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?jf1jkn$un8$1>