Date: Wed, 16 Dec 2009 20:43:56 +0100 From: Rafal Jaworowski <raj@semihalf.com> To: RuiDC <ruidc@yahoo.com> Cc: freebsd-arm@freebsd.org Subject: Re: fetch data corruption on local fs Message-ID: <1284BB72-0FAC-49E4-86FB-D44D9FD630B0@semihalf.com> In-Reply-To: <26813898.post@talk.nabble.com> References: <26803523.post@talk.nabble.com> <4B28C608.1070802@gmail.com> <4B28CFCD.3000401@semihalf.com> <26811801.post@talk.nabble.com> <4B28FF6F.4090601@semihalf.com> <26813898.post@talk.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2009-12-16, at 17:26, RuiDC wrote: > Grzegorz Bernacki wrote: >>=20 >> As I understand setting just "-o noclusterr -o noclusterw" didn't = help=20 >> you, right? If so use just "-o sync". >>=20 >=20 > I tried with three configurations: > 1. just -o sync > 2. just noclustered read/writes > 3. both sync and noclustered > All three worked, but am I correct in thinking that configuration 3 is = the > most conservative? =46rom our investigations back then disabling clustering should suffice, = forcing sync operation is a bigger hammer (against performance). > The sheevaplug build doesn't produce loader.conf or loader.4th, an ls = of my > /boot directory is below, although according to man pages for = loader.conf: > If no /boot/loader.rc exists at installworld time, one with the above = lines > will be installed.=20 >=20 > So I do not know if this is normal for a Sheevaplug build. Can anyone > confirm? > Is it OK to copy these over from an i386 machine??? > <code> > splug# ls -l /boot > total 352 > drwxr-xr-x 2 root wheel 512 Dec 15 17:04 defaults > drwxr-xr-x 2 root wheel 512 Dec 15 17:04 firmware > drwxr-xr-x 2 root wheel 512 Dec 16 13:53 kernel > -r--r--r-- 1 root wheel 13320 Dec 16 13:52 loader.help > drwxr-xr-x 2 root wheel 512 Dec 15 17:04 modules > -r-xr-xr-x 1 root wheel 166236 Dec 16 13:52 ubldr > -r-xr-xr-x 1 root wheel 166236 Dec 16 11:52 ubldr.old > drwxr-xr-x 2 root wheel 512 Dec 15 17:04 zfs > </code> It seems loader.conf and .4th are not hooked up to the ARM install = scripting/makefile; they are not required to get the loader initially = working, but you can copy them from i386 world if needed. Note that running ubldr on ARM requires the underlying U-Boot to be = compiled with CONFIG_API option enabled, which is only available in main = line U-Boot since ver. 1.3.2; what is your version? Rafal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1284BB72-0FAC-49E4-86FB-D44D9FD630B0>