bin/72787: gtar in base system doesn't seem to honor --one-file-system option

[Kirk Strauser]

>Number:         72787
>Category:       bin
>Synopsis:       gtar in base system doesn't seem to honor --one-file-system option
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Oct 17 16:10:34 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Kirk Strauser
>Release:        FreeBSD 5.3-BETA7 i386
>Organization:
The Strauser Group
>Environment:
System: FreeBSD kanga.honeypot.net 5.3-BETA7 FreeBSD 5.3-BETA7 #0: Sun Oct 10 13:47:08 CDT 2004 root at kanga.honeypot.net:/usr/obj/usr/src/sys/KANGA i386


	
>Description:
GNU tar in the base system (and the version in ports) seems to ignore the
--one-file-system option.  For example, when trying to create a tarball
of the root filesystem, it chokes on /proc (which it should be ignoring):

    root at kanga:/# gtar --one-file-system -cf /dev/null /
    gtar: Removing leading `/' from member names
    gtar: /proc: Cannot savedir: Invalid argument
    gtar: Error exit delayed from previous errors
    root at kanga:/#

bsdtar, on the other hand, works as expected:

    root at kanga:/# tar --one-file-system -cf /dev/null /
    tar: Removing leading '/' from member names
    root at kanga:/#

This is relatively recent behavior.  I had been using a 5.2.1-era system
until a few weeks ago, and only discovered this behavior after I updated
to 5.3-RC4 (and later) and my nightly Amanda backups began to fail.
>How-To-Repeat:
Attempt to create a tarball of a directory containing a mountpoint for a
proc filesystem.
	
>Fix:
	


>Release-Note:
>Audit-Trail:
>Unformatted: