From owner-freebsd-stable@FreeBSD.ORG Wed Dec 22 14:45:58 2010 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 813EF106566C for ; Wed, 22 Dec 2010 14:45:58 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from unimail.uni-dortmund.de (mx1.HRZ.Uni-Dortmund.DE [129.217.128.51]) by mx1.freebsd.org (Postfix) with ESMTP id 19D6A8FC24 for ; Wed, 22 Dec 2010 14:45:57 +0000 (UTC) Received: from [192.168.0.93] (f055206104.adsl.alicedsl.de [78.55.206.104]) (authenticated bits=0) by unimail.uni-dortmund.de (8.14.4/8.14.4) with ESMTP id oBMEjuvE020010 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for ; Wed, 22 Dec 2010 15:45:56 +0100 (CET) Message-ID: <4D120F22.7070105@FreeBSD.org> Date: Wed, 22 Dec 2010 15:45:54 +0100 From: Matthias Andree User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org References: <4D11E902.3070102@FreeBSD.org> <4D11F29F.8060108@sentex.net> <4D11FB50.5040307@FreeBSD.org> <20101222132919.GA19916@icarus.home.lan> In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: recent 8.2-STABLE commits break nullfs for tinderbox? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2010 14:45:58 -0000 Am 22.12.2010 14:53, schrieb Paul B Mahol: > On 12/22/10, Jeremy Chadwick wrote: >> On Wed, Dec 22, 2010 at 02:21:20PM +0100, Matthias Andree wrote: >>> 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. >> >> FWIW, i can't find this error message ("resource conflict avoided") >> anywhere in /usr/src, /usr/include, nor /usr/ports on RELENG_8 source >> dated from 2 hours ago. >> >> grep -ri "resource conflict" /usr/src does return some results, but >> nothing that looks identical to the string you posted. >> >> Only reason I'm pointing this out: it would be good to find the commit >> that breaks things for you, if there is such a commit, but we need >> something to key off of. > > Perhaps OP means "resource deadlock avoided"? > > Such message appears if you try to mount same mount point with nullfs > twice - which doesnt have sense. Then either tinderbox's check if the directory exists is broken, else it wouldn't retry mounting it, or something else is broken.