Bug 213335 - tar: INTERNAL ERROR: Function 'archive_read_disk_open' invoked with archive structure in state 'header', should be in state 'new/closed': Unknown error: -1
Summary: tar: INTERNAL ERROR: Function 'archive_read_disk_open' invoked with archive s...
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
: 218877 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-10-09 10:37 UTC by Wolfram Schneider
Modified: 2018-02-02 21:58 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfram Schneider freebsd_committer freebsd_triage 2016-10-09 10:37:04 UTC 

    


    


      



        
          Comment 1
        

        
          Wolfram Schneider

        

        
            freebsd_committer
            freebsd_triage
        

        
          2016-10-09 10:40:11 UTC
        

      






I got a strange error message from tar if I try to add file to an archive which don't exists.

How to repeat:

$ tar cf -  foo bar
tar: foo: Cannot stat: No such file or directory
tar: INTERNAL ERROR: Function 'archive_read_disk_open' invoked with archive structure in state 'header', should be in state 'new/closed': Unknown error: -1
tar: Error exit delayed from previous errors.

what I expected (as on MacOS with an older bsdtar)

$ tar cf - foo bar
tar: foo: Cannot stat: No such file or directory
tar: bar: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.

    


    


      



        
          Comment 2
        

        
          Wolfram Schneider

        

        
            freebsd_committer
            freebsd_triage
        

        
          2017-09-14 10:20:44 UTC
        

      






I cannot reproduce this error on -current anymore. Apparently, it was fixed.

    


    


      



        
          Comment 3
        

        
          Conrad Meyer

        

        
            freebsd_committer
            freebsd_triage
        

        
          2018-02-02 21:58:12 UTC
        

      






*** Bug 218877 has been marked as a duplicate of this bug. ***