blob: 1812d16a9bf8c6eac9e36bbab5c7aa9ed83a8ff6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
#!/bin/sh
# Ensure that du does not rely on narrow types like size_t for
# file sizes or sums.
# Copyright (C) 2003, 2005-2009 Free Software Foundation, Inc.
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
if test "$VERBOSE" = yes; then
set -x
du --version
fi
. $srcdir/test-lib.sh
require_sparse_support_
dd bs=1 seek=8G of=big < /dev/null 2> /dev/null
if test $? != 0; then
skip_test_ 'cannot create a file large enough for this test; possibly
because file offsets are only 32 bits on this file system'
fi
# FIXME: this should be a test of dd.
# On some systems (at least linux-2.4.18 + NFS to disks on a Solaris system)
# the `dd' command above mistakenly creates a file of length `0', yet
# doesn't fail. The root of that failure is that the ftruncate call
# returns zero but doesn't do its job. Detect this failure.
set x `ls -gG big`
size=$4
if test "$size" = 0; then
skip_test_ "cannot create a file large enough for this test
possibly because this system's NFS support is buggy
Consider rerunning this test on a different file system."
fi
fail=0
# This would print `0 big' with coreutils-4.5.8.
du -ab big > out || fail=1
cat <<\EOF > exp
8589934592 big
EOF
compare out exp || fail=1
Exit $fail
|
