On 09/03/11 08:31, Kevin Brott wrote:
> So this bundle seems to have the fstatat issue resolved.
OK, well, we've made progress but we may not be out of the
fstatat woods let. Let's turn to the next test failure.
Your earlier message gave these symptoms:
--- /dev/null 2011-09-01 14:53:45 -0700
+++ /lppdir/build/phs-gtar/phs-gtar/tests/testsuite.dir/at-groups/38/stderr 2011-09-01 14:53:46 -0700
@@ -0,0 +1,2 @@
+tar: .: Cannot stat: Invalid argument
+tar: Exiting with failure status due to previous errors
./extrac12.at:26: exit code was 2, expected 0
38. extrac12.at:23: 38. extract dot permissions (extrac12.at:23): FAILED (extrac12.at:26)
Is this still what testsuite.log is reporting?
Yes - this still shows the same failure message.
Can you please try this test by hand, with your tar, but use
"truss" to save the output of the two tar invocations? Something
like this:
truss -o tr1 tar --no-recursion -cf archive.tar -C src . ./file1 file2 &&
truss -o tr2 tar -xf archive.tar -C dst ...
This should isolate which "tar" is failing, and give us a clue as to why.
tar-1.26-experimental$ mkdir ftest
tar-1.26-experimental$ cd ftest
ftest$ mkdir src dst
ftest$ echo file1 >src/file1
ftest$ echo file2 >src/file2
ftest$ chmod a-w src
ftest$ truss -o tr1 ../src/tar --no-recursion -cf archive.tar -C src . ./file1 file2
ftest$ truss -o tr2 ../src/tar -xf archive.tar -C dst
../src/tar: .: Cannot stat: A system call received a parameter that is not valid.
../src/tar: Exiting with failure status due to previous errors
PS. Have you reported the bug with fstatat (AT_FDCWD, "conftest.file", &a, 0)
to the AIX folks? This time it's clearly a bug; the earlier problem is arguably
a problem with tar rather than with AIX.
truss.tar.gz