From: Jim Meyering <jim@meyering.net>
Date: Thu, 13 Mar 2003 21:05:59 +0000 (+0000)
Subject: Work around what appears to be an NFS failure that
X-Git-Tag: v4.5.10~8
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=689922fc0147b013a9ba00b1a93cd6bc0ec9795e;p=thirdparty%2Fcoreutils.git

Work around what appears to be an NFS failure that
would make this test fail on some systems.
---

diff --git a/tests/du/8gb b/tests/du/8gb
index bd6ffb3b8a..1400369969 100755
--- a/tests/du/8gb
+++ b/tests/du/8gb
@@ -30,6 +30,20 @@ if test $? != 0; then
   (exit 77); exit 77
 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
+  echo "$0: cannot create a file large enough for this test;" 1>&2
+  echo "$0: possibly because this system's NFS support is buggy;" 1>&2
+  echo "$0: Consider rerunning this test on a different file system." 1>&2
+  (exit 77); exit 77
+fi
+
 fail=0
 
 # This would print `0	big' with coreutils-4.5.8.