Hi, another word on the issue: I just dug into the tar mailing-list archives and found this nugget:
(https://lists.gnu.org/archive/html/bug-tar/2016-03/msg00013.html) > I was running "make check" on tar built from the latest git, and found > that sparse05.at doesn't fail gracefully when my build partition runs > out of space during the test. > > Specifically, my partition started out with 2.3G free. The test tried > to run, and managed to create a BIGFILE 4893794304 bytes in listed size > before the partition filled up... at which point the test failed with: > > ./testsuite: line 1584: echo: write error: No space left on device > 142. sparse05.at:21: 142. listing sparse files bigger than 2^33 > B(sparse05.at:21): FAILED (sparse05.at:31) > > Unfortunately, after that failure, the BIGFILE is left on the disk, > and > all the following tests also fail with "no space left on device" > messages. > > I will try to run the tests again with more space, but I wonder if > there > is some way for sparse05.at to fail more gracefully in this > situation. I wonder, do people simply ignore the tar testsuite, or do they all put their LFS in large enough partitions? Chapter 2.4 talks about 6GB minimum, but says that a "20 GB partition is a reasonable size to provide for growth". I guess I was just the unlucky guy who took things a bit too literally, lol. Cheers Chris -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
