Discussion:
[lfs-support] LFS Stable 5.31.1 tar-1.30 Testsuite filled up my partition
Christian Friedl
2018-09-09 10:59:49 UTC
Permalink
Ths is my third attempt to create a LFS, finally
heeding the sage advice to put it all into repeatable scripts (thank
goodness for that!).

Just a little incident report:

I included a "make check" everywhere even in chapter 5, just to be on
the safe side. Started the scripts and went for a few beers.


* After coming back, I found lots of "No space left on device" warnings in
the logs.

* It would seem that the testsuite for tar (Chapter 5.31: Tar-1.30)
created one gigantic file, aptly named BIGFILE, that ate up my whole lfs
partition (all of 5.3GB that were left at that point).

I will investigate the issue later this week and keep you posted, for
now I just disabled the testsuite, since it's marked optional in the
book and it's only the temp system.

Regards
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?

ht
Bruce Dubbs
2018-09-09 17:06:35 UTC
Permalink
Post by Christian Friedl
Ths is my third attempt to create a LFS, finally
heeding the sage advice to put it all into repeatable scripts (thank
goodness for that!).
I included a "make check" everywhere even in chapter 5, just to be on
the safe side. Started the scripts and went for a few beers.
* After coming back, I found lots of "No space left on device" warnings in
the logs.
* It would seem that the testsuite for tar (Chapter 5.31: Tar-1.30)
created one gigantic file, aptly named BIGFILE, that ate up my whole lfs
partition (all of 5.3GB that were left at that point).
I will investigate the issue later this week and keep you posted, for
now I just disabled the testsuite, since it's marked optional in the
book and it's only the temp system.
Are you removing the expanded package directories after each package?

tar -xf package.tar.xz
cd package
build instructions
cd ..
rm -rf package

-- Bruce
--
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?
Christian Friedl
2018-09-10 06:50:19 UTC
Permalink
Hi Bruce,

thanks for your quick reply!
Post by Bruce Dubbs
Are you removing the expanded package directories after each package?
Oh, yes. I forgot it in about 3 or 4 scripts, but that didn't impact the
build process a lot.

For investigation, I just ran make check check on a newly wget'ed (wgotten?)
tar-1.30.tar.xz on my virtual machine in the cloud.

"Test # 154: listing sparse files bigger than 2^33 B" created a file
named tests/testsuite.dir/154/pax/BIGFILE, that grew to a whopping 20 GB
/ 20961034240 B before the test finished.

The test name kind of implies this, of course. How do people get this
thing to go through on limited space? (20GB is not that much this day
and age, but still, I'd never have guessed I'd need that much space for
setting up an LFS).

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.or
Christian Friedl
2018-09-10 06:59:56 UTC
Permalink
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
./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_
Ken Moffat
2018-09-10 15:09:21 UTC
Permalink
Post by Christian Friedl
For investigation, I just ran make check check on a newly wget'ed (wgotten?)
tar-1.30.tar.xz on my virtual machine in the cloud.
"Test # 154: listing sparse files bigger than 2^33 B" created a file
named tests/testsuite.dir/154/pax/BIGFILE, that grew to a whopping 20 GB
/ 20961034240 B before the test finished.
The test name kind of implies this, of course. How do people get this
thing to go through on limited space? (20GB is not that much this day
and age, but still, I'd never have guessed I'd need that much space for
setting up an LFS).
From building in a 10GB partition:

153: storing long sparse file names ok
154: listing sparse files bigger than 2^33 B ./testsuite: line 1901: echo: write error: No space left on device
skipped (sparse05.at:31)
155: storing sparse file using seek method ok

But it cleaned up fine and there was only one other error. And
since nothing else was using that filesystem at the time, no
problems.

ĸen
--
Also Spuke Zerothruster
(Finnegans Wake)
--
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?
Michael Shell
2018-09-10 12:14:45 UTC
Permalink
On Sun, 9 Sep 2018 12:59:49 +0200
Post by Christian Friedl
* It would seem that the testsuite for tar (Chapter 5.31: Tar-1.30)
created one gigantic file, aptly named BIGFILE, that ate up my whole lfs
partition (all of 5.3GB that were left at that point).
IMHO, we should add a warning to the tar page about that.


Cheers,

Mike Shell
--
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://
Bruce Dubbs
2018-09-10 16:52:50 UTC
Permalink
Post by Michael Shell
On Sun, 9 Sep 2018 12:59:49 +0200
Post by Christian Friedl
* It would seem that the testsuite for tar (Chapter 5.31: Tar-1.30)
created one gigantic file, aptly named BIGFILE, that ate up my whole lfs
partition (all of 5.3GB that were left at that point).
IMHO, we should add a warning to the tar page about that.
The problem is in Chapter 5 and not in Chapter 6. We already say:

Experience has shown that there is little to be gained from running the
test suites in Chapter 5. There can be no escaping the fact that the
host system always exerts some influence on the tests in that chapter,
often causing inexplicable failures. Because the tools built in Chapter
5 are temporary and eventually discarded, we do not recommend running
the test suites in Chapter 5 for the average reader. The instructions
for running those test suites are provided for the benefit of testers
and developers, but they are strictly optional.

I do not want to start documenting failures that may be host system
dependent.

-- Bruce
--
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?

htt
Michael Shell
2018-09-11 05:23:56 UTC
Permalink
On Mon, 10 Sep 2018 11:52:50 -0500
Post by Bruce Dubbs
I do not want to start documenting failures that may be host system
dependent.
OK, but what about chapter 6? Make check is recommended there (actually
make check is also shown in chapter 5.31) and it is going to require such
an unexpectedly large amount of space. 6GB is the required minimum
according to chapter 2.4 "Creating a New Partition".


Cheers,

Mike
--
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 thin
Bruce Dubbs
2018-09-11 05:54:19 UTC
Permalink
Post by Michael Shell
On Mon, 10 Sep 2018 11:52:50 -0500
Post by Bruce Dubbs
I do not want to start documenting failures that may be host system
dependent.
OK, but what about chapter 6? Make check is recommended there (actually
make check is also shown in chapter 5.31) and it is going to require such
an unexpectedly large amount of space. 6GB is the required minimum
according to chapter 2.4 "Creating a New Partition".
I've never seen the problem in Chapter 6. I generally use a 10G
partition, so it the file is that big, then it should be a problem.

On a partition with 2G of free space, no tests failed for me. I did get:
...
154: listing sparse files bigger than 2^33 B ./testsuite: line
1901: echo: write error: No space left on device
skipped (sparse05.at:31)
...
206 tests were successful.
14 tests were skipped.

-- Bruce
--
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/
Loading...