Date: Wed, 19 May 2010 12:29:52 +0200 From: Rafal Jaworowski <raj@semihalf.com> To: Matthias Reyelt <Matthias.Reyelt@brunel.de> Cc: freebsd-arm@freebsd.org Subject: Re: files damaged on memory disk on Marvell Discovery 78100 Message-ID: <9E1BDCD0-CBE1-46D8-AECC-AE9E277C86B7@semihalf.com> In-Reply-To: <201005190820.00413.Matthias.Reyelt@brunel.de> References: <201005190820.00413.Matthias.Reyelt@brunel.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2010-05-19, at 08:19, Matthias Reyelt wrote: > I have observed a strange behaviour on the Marvell Discovery: >=20 > I have a memory disk for /etc and /opt: > /dev/md0 on /etc (ufs, local) > /dev/md1 on /opt (ufs, local) >=20 > When I copy files to that disk, which are larger than 0x1ffff (131071 = bytes),=20 > these files differ from the original. This occurs only when copying to = md.=20 >=20 > Kernel is: > FreeBSD discovery1 8.0-STABLE FreeBSD 8.0-STABLE #0 r206836: Mon Apr = 19=20 > 12:53:42 CEST 2010 =20 > root@vbcspc12.bcs.brunel.local:/usr/obj/arm/root/ARM/8/sys/DB-78XXX = arm >=20 > I had a look into the damaged file and found some excerpts from files = located=20 > in /etc (which is also in RAM): > ------------------------------------------------------------ > passwd: compat > passwd_compat: nis > shells: files > ----------------------------------------------------------------- > ... > ----------------------------------------------------------------- > staff:*:20: > sshd:*:22: > smmsp:*:25: > mailnull:*:26: > guest:*:3-=EF=BF=BD=EF=BF=BD=EF=BF=BD=0F > ------------------------------------------------------------------ >=20 > Looks as if the CPU has problems accessing the RAM. I have already = changed the=20 > RAM, so I don't think it's a hardware problem.=20 >=20 > Any idea? Try turning off clustering on the filesystem(s). There was least one = known problem in this area leading to cache incoherency, see this thread = for more details (and how-to): = http://lists.freebsd.org/pipermail/freebsd-arm/2008-December/001423.html Rafal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9E1BDCD0-CBE1-46D8-AECC-AE9E277C86B7>