Date: Sun, 12 Mar 2017 21:32:29 +0100 From: Milan Obuch <freebsd-arm@dino.sk> To: Ian Lepore <ian@freebsd.org> Cc: =?ISO-8859-1?Q?Otac=EDlio?= <otacilio.neto@bsd.com.br>, freebsd-arm@freebsd.org Subject: Re: FreeBSD on Pine64 experience Message-ID: <20170312213229.25ed338e@zeta.dino.sk> In-Reply-To: <1489340940.40576.84.camel@freebsd.org> References: <20170220124619.7f04ad6a@zeta.dino.sk> <20170224182831.76c15809@zeta.dino.sk> <20170312174353.13e1110d@zeta.dino.sk> <fe13db5d-01ac-1e96-3d9e-e6d691193a92@bsd.com.br> <1489340940.40576.84.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 12 Mar 2017 11:49:00 -0600 Ian Lepore <ian@freebsd.org> wrote: > On Sun, 2017-03-12 at 14:05 -0300, Otac=EDlio wrote: > > Em 12/03/2017 13:43, Milan Obuch escreveu: =20 [ snip ] > > > This problem is solved, discussion was on hackers mailing list, > > > basically mount option nolockd was the clue. However, on Pine64, I > > > am > > > getting now occasional errors > > >=20 > > > pid 12421 (sh), uid 0, was killed: text file modification > > >=20 > > > preventing me to rebuild some port or source if tree is mounted > > > over > > > nfs. I remember mentioning on some mailing list it could be > > > related to > > > nfs, today I decide to use HDD attached via USB for ports tree and > > > no > > > error occured. So this definitely means there is something in nfs > > > code, > > > probably arm64 specific as I did not see something like this on > > > arm system, which causes this error. [ snip ] > > I faced this same problem about "text file modification" on a RPI3 > > take=A0 > > a look: > >=20 > > https://lists.freebsd.org/pipermail/freebsd-arm/2017-March/015789.htm > > l > >=20 > > []'s > >=20 > > -Otacilio > > =20 >=20 > Another thread related to the same problem: >=20 > https://lists.freebsd.org/pipermail/freebsd-current/2017-March/065131.html >=20 > As I mentioned there just now, it may be possible to work around this > with sysctl vfs.timestamp_precision, but I'm not sure exactly how. >=20 > -- Ian >=20 Thanks, setting 'sysctl vfs.timestamp_precision=3D0' seems to solve this issue for me. At least I was able to rebuild misc/mc port with no error messages, just pkg still says # pkg check -d -a Checking all packages: 100% mc is missing a required shared library: libglib-2.0.so.0 mc is missing a required shared library: libssh2.so.1 mc is missing a required shared library: libintl.so.8 I am going to try world rebuild with this setup. regards, Milan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170312213229.25ed338e>