From owner-freebsd-current@FreeBSD.ORG Thu Aug 30 14:07:50 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AB0EE106564A for ; Thu, 30 Aug 2012 14:07:50 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 27CC98FC08 for ; Thu, 30 Aug 2012 14:07:49 +0000 (UTC) Received: by wicr5 with SMTP id r5so265650wic.13 for ; Thu, 30 Aug 2012 07:07:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=GOe4R81lCnvzgi0oi2RGnbFhBUMohdaSbRNrtIjDcBA=; b=eCMuF49RcPSrZyoh6Q3u8mE0QhtJzVUKJ92NTPh51jHO1aa5oFzvtQRgn3XeG/J3Xu TAt9YOJKzbdgdsviQAoqIYNWyw4c4tKSPwMXP0OAgN+zXg/Mou5P8RCVzfpGkQAoUFGT 2OtSQSBES777UelbQYKet2cKgvnAYTC6/9pII= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=GOe4R81lCnvzgi0oi2RGnbFhBUMohdaSbRNrtIjDcBA=; b=USGWkhL7kpevgLOuggTcyp3QHN4q6pckP/PdWNolsNX0YNghdlCFC2aOj1sNzzHDeU PXQSe8YAXGok6jsDjyOITYn63laDdtGIIaZQHHrG2gFD2cpURzB27RoFcXXEXSX/e8uD tkpOxVSwQSOQMwnGrh7rlkTVdFbd7+MjeomjMrpziDwMLu9Pdnb3bk0WfXB3Y2KzNQrM eLD+i3z9TF3eax8E4/F/+AtC7UYMrIUMAWkfiQdQZaA/a0zTdNVxgpkk9+oHmhmW4QLS A5iUDQgC37Zb/h9p/1oDNRShXR+oldt+RnYdZy39ttrzllsM+4HUMzmmtSzl+Ot8dmQ5 4dSg== MIME-Version: 1.0 Received: by 10.216.52.213 with SMTP id e63mr2761615wec.205.1346335668811; Thu, 30 Aug 2012 07:07:48 -0700 (PDT) Sender: decke@bluelife.at Received: by 10.180.90.15 with HTTP; Thu, 30 Aug 2012 07:07:48 -0700 (PDT) X-Originating-IP: [80.123.233.199] In-Reply-To: <20120820123142.GY33100@deviant.kiev.zoral.com.ua> References: <20120812132047.GA33526@psconsult.nl> <20120820123142.GY33100@deviant.kiev.zoral.com.ua> Date: Thu, 30 Aug 2012 16:07:48 +0200 X-Google-Sender-Auth: M_PSs5DM284PlvUxwd7XwvJxuvg Message-ID: From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= To: Konstantin Belousov Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnl5kV+icRU2JmsMLyyiSHtTo7ZlYJs+djcQvyD2B2ktIevFoLyKW59fK2dISsCj58mxnnO Cc: Garrett Cooper , Current FreeBSD , Paul Schenkeveld Subject: Re: make package fails in chroot: tar: getvfsbyname failed: No such file or directory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 30 Aug 2012 14:07:50 -0000 On Mon, Aug 20, 2012 at 2:31 PM, Konstantin Belousov wrote: > On Mon, Aug 20, 2012 at 01:42:31PM +0200, Bernhard Fr?hlich wrote: >> On Sun, Aug 19, 2012 at 10:01 PM, Tim Kientzle wrote: >> > >> > On Aug 19, 2012, at 12:17 PM, Garrett Cooper wrote: >> > >> >> On Sun, Aug 19, 2012 at 9:45 AM, Tim Kientzle wrote: >> >>> >> >>> On Aug 12, 2012, at 6:20 AM, Paul Schenkeveld wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> I have a wrapper script that builds packages in a chroot environment >> >>>> which happily runs on release 6 thru 9 and earlier 10 but fails with: >> >>>> >> >>>> tar: getvfsbyname failed: No such file or directory >> >>>> >> >>>> on a recent -CURRENT. >> >>> >> >>> libarchive does do an initial getvfsbyname() when you ask it >> >>> to traverse a directory tree so that it can accurately handle later >> >>> requests about mountpoints and filesystem types. This code >> >>> is admittedly a little intricate. >> >> >> >> The problem most likely is the fact that all mountpoints are >> >> exposed via chroot, thus, if it's checking to see if a mountpoint >> >> exists, it may exist outside of the chroot. >> >> >> > >> > I reviewed the code to refresh my memory. Some >> > of what I said before was not quite right. >> > >> > Libarchive's directory traversal tracks information about >> > the filesystem type so that clients such as bsdtar can >> > efficiently skip synthetic filesystems (/dev or /proc) or >> > network filesystems (NFS or SMB mounts). >> > >> > The net effect is something like this: >> > >> > For each file: >> > stat() or lstat() or fstat() the file >> > look up dev number in an internal cache >> > if the dev number is new: >> > fstatfs() the open fd to get the FS name >> > getvfsbyname() to identify the FS type >> > >> > Unless there's a logic error in libarchive itself, this >> > would suggest that somehow fstatfs() is returning >> > a filesystem type that getvfsbyname() can't >> > identify. >> > >> > Paul: >> > What filesystem are you using? >> > >> > What does "mount" show? >> > >> > Does it work outside the chroot? >> >> I also see the same on the redports.org build machines. >> It builds within a jail there which is completely on a tmpfs. >> Interestinly everything is fine with a 10-CURRENT/amd64 >> jail but it breaks in a 10-CURRENT/i386 jail. Both are >> running on the same 10-CURRENT/amd64 which is >> around 2 months old. >> >> https://redports.org/buildarchive/20120814130205-56327/ > > Try this. Is it possible that this requires the host system to be quite new? The commit in HEAD seems to doesn't help in my case. Host is 9-stable from Jun 27 and jail is 10-current from a few days ago. -- Bernhard Froehlich http://www.bluelife.at/