[Bug 262293] sysutils/archivemount gives errors after mounting the 13.0 release tarballs
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262293] sysutils/archivemount gives errors after mounting the 13.0 release tarballs"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262293] sysutils/archivemount gives errors after mounting the 13.0 release tarballs"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262293] sysutils/archivemount gives errors after mounting the 13.0 release tarballs"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262293] sysutils/archivemount gives errors after mounting the 13.0 release tarballs"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262293] sysutils/archivemount gives errors after mounting the 13.0 release tarballs"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262293] sysutils/archivemount gives errors after mounting the 13.0 release tarballs"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 02 Mar 2022 10:05:02 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262293
Bug ID: 262293
Summary: sysutils/archivemount gives errors after mounting the
13.0 release tarballs
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs@FreeBSD.org
Reporter: billblake2018@gmail.com
CC: jirnov@gmail.com
Flags: maintainer-feedback?(jirnov@gmail.com)
CC: jirnov@gmail.com
It occurred to me that I could save oodles of disk space (and, for certain
operations, speed things up) by using archivemount to mount compressed archives
of /usr/ports and /usr/src. This is on FreeBSD 13.0 with the archivemount
0.8.12 package. I issued the command:
archivemount -o readonly ports.txz /mnt
Ports.txz being the release tarball for 13.0. An ls of /mnt/usr/ports gave the
expected results. However, running du -s /mnt gave a long stream of "No such
file or directory" error messages for items that actually existed if I cd'd and
looked. I tried a gzipped version of the tarball. Same thing. So I tried an
uncompressed tar file. Ditto. Then I zipped up /usr/ports and tried the zip
file. Ditto. I tried the src tarball. Ditto.
Then I tried the base tarball. A du -s /mnt gave a plausible result; I didn't
check it. Because after I ran that command, all further commands returned
"Input/output error". Ditto when I tried the uncompressed tarball. However,
it did seem to behave with the kernel tarball.
Next, I tarred the base, kernel, src, and ports tarball and tried that tar
file. All good, so it isn't just a matter of the archive size. I tarred up
/usr/ports/devel (the directory with the largest number of entries) and tried
that. No problem, so it isn't just a matter of a large number of directory
entries in a directory.
I left it at that and prepared this PR.
--
You are receiving this mail because:
You are the assignee for the bug.