Date: Wed, 22 Dec 2010 14:21:20 +0100 From: Matthias Andree <mandree@FreeBSD.org> To: freebsd-stable@FreeBSD.org Subject: Re: recent 8.2-STABLE commits break nullfs for tinderbox? Message-ID: <4D11FB50.5040307@FreeBSD.org> In-Reply-To: <4D11F29F.8060108@sentex.net> References: <4D11E902.3070102@FreeBSD.org> <4D11F29F.8060108@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 22.12.2010 13:44, schrieb Mike Tancsa: > On 12/22/2010 7:03 AM, Matthias Andree wrote: >> Greetings, >> >> I'm tracking 8.2-PRERELEASE, and it appears that recent commits to nullfs, zfs, >> vfs, or thereabouts have broken Tinderbox for me. >> >> I'm mounting my ports tree via nullfs, which has been working fine for a year. >> >> Any ideas, or further info needed? > > Hi, > Whats specifically broken ? Two of the freebsd tinderbox machines are > RELENG_8 from Dec 3 and they are fine. However, they dont use nullfs, > just zfs and ufs. Is it just nullfs thats broken ? What are the errors > you are getting ? I updated after that. mount_nullfs /usr/ports.cvs /usr/local/tinderbox/portstrees/FreeBSD/ports fails with "resource conflict avoided". I'll now rebuild GENERIC from scratch (including "make clean") to see if that helps. Tried switching to NFS, this appears to work now.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D11FB50.5040307>