On Wednesday 02 of December 2015 08:15:41 Pavel Raiskup wrote: > On Wednesday 02 of December 2015 01:04:37 Budi Setiawan wrote: > > plz check > > need answer for my lfs project thx > > Please don't attach uncompressed testsuite.log [1]. > > | uname -m = i686 > | uname -r = 3.19.0-33-generic > | uname -s = Linux > | uname -v = #38~14.04.1-Ubuntu SMP Fri Nov 6 18:17:49 UTC 2015 > | > | > | 128. sparse03.at:21: testing storing sparse files > 8G ... > | ./sparse03.at:29: > | mkdir posix > | (cd posix > | TEST_TAR_FORMAT=posix > | export TEST_TAR_FORMAT > | TAR_OPTIONS="-H posix" > | export TAR_OPTIONS > | rm -rf * > | > | genfile --length 1000 --file begin > | genfile --length 1000 --file end > | genfile --sparse --file sparsefile --block-size 512 8G A || exit 77 > | tar -c -f archive --sparse begin sparsefile end || exit 1 > | echo separator > | > | tar tfv archive > | echo separator > | mkdir directory > | tar Cxf directory archive > | genfile --stat=name,size sparsefile > | cmp sparsefile directory/sparsefile > | ) > | --- /dev/null 2015-12-01 14:34:19.258291399 +0000 > | +++ /mnt/lfs/sources/tar-1.28/tests/testsuite.dir/at-groups/128/stderr > 2015-12-01 17:51:17.521183405 +0000 > | @@ -0,0 +1,2 @@ > | +tar: sparsefile: Cannot open: Value too large for defined data type > | +tar: Exiting with failure status due to previous errors > > Looks like tar is not able to open 'sparsefile' (big sparse file). > Could you check why '#define _FILE_OFFSET_BITS 64' is not used in your > config.h (or why, for some reason, _FILE_OFFSET_BITS=64 is not used) [2]? > Based on the testsuite.log, it looks _FILE_OFFSET_BITS=64 is defined. > > [1] https://lists.gnu.org/archive/html/bug-tar/2014-01/msg00021.html > [2] > http://www.gnu.org/software/coreutils/faq/coreutils-faq.html#Value-too-large-for-defined-data-type
JFYI: I observed this behavior recently on Fedora 23 i386: https://bugzilla.redhat.com/show_bug.cgi?id=1288662 # rpm -q glibc glibc-2.22-5.fc23.i686 Pavel
