Date: Sun, 30 Mar 2025 17:35:48 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 285783] bsdtar returns non-zero when extracting archive containing entry with creation time near the epoch Message-ID: <bug-285783-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285783 Bug ID: 285783 Summary: bsdtar returns non-zero when extracting archive containing entry with creation time near the epoch Product: Base System Version: 14.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: janm@transactionware.com After creating an archive with the command: $ sudo bsdtar -c -f ../test.tar --one-file-system --format pax --exclude '\./tmp/\*' . When the source directory, contains a 'dev' entry, with a mounted devfs, the following error is given when attempting to read the archive: $ bsdtar tf test.tar > /dev/null bsdtar: (null) bsdtar: Error exit delayed from previous errors. Creating the archive with the same command, but no mounted devfs, works correctly. After some simple investigation, I see this attribute added for the ./dev/ entry with devfs mounted: LIBARCHIVE.creationtime=-1.27 Archives created with and without the devfs filesystem mounted have valid ctime attributes. This is a jail image, created and archived using a build system with a long history. This issue was not present in 13.3 and many earlier versions. The source file system is on ZFS, on a new 14.2-RELEASE system. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-285783-227>