From owner-freebsd-stable@FreeBSD.ORG Thu Mar 6 13:52:15 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C223DC3 for ; Thu, 6 Mar 2014 13:52:15 +0000 (UTC) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6C84276C for ; Thu, 6 Mar 2014 13:52:15 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 045F0214AE; Thu, 6 Mar 2014 08:52:12 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute2.internal (MEProxy); Thu, 06 Mar 2014 08:52:12 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=oZXsySRJS4CFjIU3xAFB5fd8F0Y=; b=NY8g3 +7DV/Zk5F7T2OX/f45akV5sCu6yKtPv1koWuf8GW7IiX13GZ02bEScT0F8Pp4WH2 COf2NymQrY0njBOF7IXWL0CiaeL/g2cMa69cfnhR8RBTBY/Vfy/wyHhcZqb66ezc Gkr5JxMSjUpObPUCxSx5LXJfLdYd6963bJoWrc= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id CE94B106A44; Thu, 6 Mar 2014 08:52:11 -0500 (EST) Message-Id: <1394113931.5425.91315465.02C64673@webmail.messagingengine.com> X-Sasl-Enc: oDYNbjuSu0BxE9X0D/ooQZAhMyO3DUTd6kia/EzwuLvV 1394113931 From: Mark Felder To: "Marat N.Afanasyev" , Ronald Klop , freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-4527a23f Subject: Re: bsdtar POLA change in 10.0? Date: Thu, 06 Mar 2014 07:52:11 -0600 In-Reply-To: <53187C28.9080707@ksu.ru> References: <53171DAE.5070203@li.ru> <1394110822.21224.91297125.0B659AFB@webmail.messagingengine.com> <1394111704.25672.91302321.2D5C71E3@webmail.messagingengine.com> <53187C28.9080707@ksu.ru> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2014 13:52:15 -0000 On Thu, Mar 6, 2014, at 7:46, Marat N.Afanasyev wrote: > Mark Felder wrote: > > > > > > On Thu, Mar 6, 2014, at 7:12, Ronald Klop wrote: > >> On Thu, 06 Mar 2014 14:00:22 +0100, Mark Felder wrote: > >> > >>> > >>> > >>> On Wed, Mar 5, 2014, at 6:50, Marat N.Afanasyev wrote: > >>>> I wonder why > >>>> > >>>> bsdtar --one-file-system > >>>> > >>>> suddenly started to skip archiving of mount-points? And no mention of > >>>> such behaviour change either in UPDATING or errata :( > >>>> > >>> > >>> --one-file-system > >>> (c, r, and u modes) Do not cross mount points. > >>> > >>> Isn't that what it's supposed to do? Skip any mounted filesystems? Was > >>> it broken before? Or do I simply not understand the behavior you're > >>> seeing. > >> > >> The question is if the mountpoint (directory in the 'current' filesystem) > >> itself should be tarred. After untarring you can than make the same > >> mounts > >> again, for example. > >> > > > > So you're saying that if I have a disk mounted at /mnt/disk and my tar > > with --one-file-system includes /mnt, the empty directory /mnt/disk will > > not be in the tarball? > > Yes, your /mnt/disk will not be in archive, while older version > certainly pick this directory > After some minor sleuthing I wonder if this commit could be the culprit https://github.com/libarchive/libarchive/commit/3439b41d9252372753dc8ca2c7b3e6c0dcfc2874 I don't have the free time to test further at the moment, but attempting to reverse that commit on the libarchive in /usr/src/contrib and then rebuilding bsdtar would be an interesting experiment.