https://sourceware.org/bugzilla/show_bug.cgi?id=31729
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
Maybe we should just up the test to try to get at least 200MB or 500MB? So
change the timeout from 10s to 5s or 2s ? Locally timeout -s9 2s dd conv=fsync
if=/dev/zero of=tempfile bs=1M count=1K works just fine.
But trying to find a different location/file system for the tests sound OK too.
Note that there are two tests to see if the location/disk can be used:
# These tests need lots of disk space since they test files > 4GB.
# Skip if there just isn't enough (2.5 * 4 = 10GB).
space_available=$[$(stat -f --format="%a*%S" .)/(1024 * 1024 * 1024)]
echo "space_available: $space_available"
if test $space_available -lt 10; then
echo "Not enough disk space, need at least 10GB available"
exit 77
fi
and
# Make sure the disk is reasonably fast, should be able to write 100MB/s
fast_disk=1
timeout -s9 10s dd conv=fsync if=/dev/zero of=tempfile bs=1M count=1K \
|| fast_disk=0; rm tempfile
if test $fast_disk -eq 0; then
echo "File system not fast enough, need at least 100MB/s"
exit 77
fi
They probably should be combined and then tried on some reasonable sounding
locations, "/var/tmp", "/tmp" and "." ? Then pick the one with the highest
speed?
--
You are receiving this mail because:
You are on the CC list for the bug.
