From owner-freebsd-stable@FreeBSD.ORG Wed Dec 22 14:21:18 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 4B20C106564A; Wed, 22 Dec 2010 14:21:18 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id D44468FC18; Wed, 22 Dec 2010 14:21:17 +0000 (UTC) Received: by qwj9 with SMTP id 9so4951087qwj.13 for ; Wed, 22 Dec 2010 06:21:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=tVJyKPWsxcbFsaHGVjqeRimaF4Nt6juuggBCA/8O4QU=; b=ChTLWRy6DgXJoRtr/qSagDcokNO5SoA1p2iShduiqHFuuyywmUsrj607GhpWMapprz dSklXkl4o2x0uuHETXJpRw7eJMtfdIf+7R/P+InS0bGC7uFiEwtd9VYUNR0OQVjGAFbC fzLy8GOCP24C+mo7cJQkreFIm9LZTNm0U6AVw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=IGyyU0Z1ctQi+ZzZoEYuzS/q1dRh/dthnt9ZFDqaw6EOFDH41/BJjOff9lKkowXcje +5ABkreV8LQlkJgZEn6kNkHNztZnGBZT1cPKBMv1kaspIOueuA992iW22xBD65JmdoxT nF0zU6JUuAcSBbaCmDSkH6nvmVsqxt9gUN06I= MIME-Version: 1.0 Received: by 10.224.11.68 with SMTP id s4mr6358451qas.385.1293026020328; Wed, 22 Dec 2010 05:53:40 -0800 (PST) Received: by 10.220.175.141 with HTTP; Wed, 22 Dec 2010 05:53:40 -0800 (PST) In-Reply-To: <20101222132919.GA19916@icarus.home.lan> References: <4D11E902.3070102@FreeBSD.org> <4D11F29F.8060108@sentex.net> <4D11FB50.5040307@FreeBSD.org> <20101222132919.GA19916@icarus.home.lan> Date: Wed, 22 Dec 2010 13:53:40 +0000 Message-ID: From: Paul B Mahol To: Jeremy Chadwick Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, Matthias Andree 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:21:18 -0000 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.