From owner-freebsd-current@FreeBSD.ORG Fri Apr 19 14:57:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 74DD2567; Fri, 19 Apr 2013 14:57:41 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ea0-x230.google.com (mail-ea0-x230.google.com [IPv6:2a00:1450:4013:c01::230]) by mx1.freebsd.org (Postfix) with ESMTP id D991669F; Fri, 19 Apr 2013 14:57:40 +0000 (UTC) Received: by mail-ea0-f176.google.com with SMTP id h14so1191061eak.35 for ; Fri, 19 Apr 2013 07:57:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=DaZXHyhzBqvKiQE/H+RKkvQKCzOaKsSfpgzzqoqPNZw=; b=ituMZG6yVXawasNtvzLNpn84hd3pzgnMqB2mZjKNc5jgOeIgGSPGW19/hnaGPRH+mF thOFlHmX4FjX1upBWxrpdbAfQI/ghHqH38AIvtDR5TmbbXhgCya5vnAWgtOAbnxKkE0J 3I08sLykBr9fsxFmsuhXdu84ywt3+rJ/O54hKdSPR0mv+zMyLMEOX97fOnIw/IMJ6kAM kXrBqLl7hF3JaEnWWC+YEzX37cyFy2CPhdxxXrh/QyiXNS+z7BiKN8K91e3ii6R69ZDJ FEeGhdr25/QIQZpBFZCL2m0J2NDJqWDpAkLI+mjj6fWjYrAFDCtjZ+7ajaiOsyqsroPW /+0w== MIME-Version: 1.0 X-Received: by 10.15.76.132 with SMTP id n4mr11083851eey.16.1366381810700; Fri, 19 Apr 2013 07:30:10 -0700 (PDT) Sender: hiren.panchasara@gmail.com Received: by 10.15.91.72 with HTTP; Fri, 19 Apr 2013 07:30:09 -0700 (PDT) Received: by 10.15.91.72 with HTTP; Fri, 19 Apr 2013 07:30:09 -0700 (PDT) In-Reply-To: References: Date: Fri, 19 Apr 2013 07:30:09 -0700 X-Google-Sender-Auth: LsXakADcAMEoVNg_hXnX9Vww1ZA Message-ID: Subject: Re: Cannot unmount nullfs in current From: hiren panchasara To: Craig Rodrigues Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Apr 2013 14:57:41 -0000 On Apr 18, 2013 7:04 PM, "Craig Rodrigues" wrote: > > Hi, > > I am trying to build some software which uses > nanobsd, and mounts/unmounts many nullfs mounts > while it runs. I am hitting failures where > I cannot unmount nullfs file systems. I cannot figure out why. I am also getting similar failures while trying to build freenas. > > Here is more info. > > SYSTEM > ====== > I am running amd64, current build at this revision: > > 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r249181: Sat Apr 6 03:07:32 UTC 2013 > amd64 > > STEPS TO REPRODUCE > =============== > > (1) Create a directory, /opt2/branches. Make sure that /opt2/branches > is on ZFS > > (2) > mkdir -p /opt2/branches/freenas > mkdir -p /opt2/branches/freenas-cache > > (3) > > git clone git://github.com/freenas/freenas.git /opt2/branches/freenas > git clone git:// github.com/freenas/ports.git/opt2/branches/freenas-cache/ports > git clone git:// github.com/trueos/trueos.git/opt2/branches/freenas-cache/trueos > > (4) sudo to root > > (5) cd /opt2/branches/freenas > > (6) > script build.log env GIT_REPO=/opt2/branches/freenas-cache/trueos \ > GIT_PORTS_REPO=/opt2/branches/freenas-cache/ports \ > sh build/do_build.sh > > > The build cranks for a while, and then I get this error: > > 00:02:37 ### log: > /opt2/branches/freenas/os-base/amd64/_.cust.add_pkg_archivers_lzo2 I do not get this. > do_build.sh: ERROR: FreeNAS /opt2/branches/freenas/nanobsd/os-base build > FAILED; please check above log for more details I get this which looks like a generic build failure message. I do not have gnome or any X related things. > > > > If I look in .cust.add_pkg_archivers_lzo2, I see this error: > > + umount /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles > umount: unmount of > /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles failed: Device > busy Where do you find/see logs for the build? Another weird thing. Somehow my /sbin was wiped out and only had some pbi-* files in it. This happened to me on 2 different machines while trying to build freenas. I will try to take a closer look today when time permits. Thanks, Hiren > > > If I try to do this manually: > > # umount /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles > umount: unmount of > /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles failed: Device > busy > > > I can't figure out why this mount is busy. > If I do: > > umount -f /opt2/branches/freenas/os-base/amd64/_.w/usr/ports/distfiles > > it unmounts, but I don't like using the '-f' flag to force the unmount. > > Any ideas? I am attaching some of my logs. > > -- > Craig > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"