From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: connectathon test failures
Date: Wed, 8 Oct 2008 18:55:43 -0400 [thread overview]
Message-ID: <20081008225543.GG14527@fieldses.org> (raw)
I'm getting connectathon test failures with the latest merge of code
from both our trees, linux-to-linux over v3 and v4.
I just got this a moment ago, so haven't tried to track it down at all
yet--but I seem to recall in the past this sort of failure has been an
attribute revalidation problem (usually with the ext3 ctime resolution
at least partly to blame).
--b.
----- Forwarded message from git-KezNCC8cqm5ZN1qrTdtDg5Vzexx5G7lz@public.gmane.org -----
Linux ying3 2.6.27-rc9-00096-gb6ae157 #77 PREEMPT Wed Oct 8 18:24:11 EDT 2008 i686 GNU/Linux
cthon: local filesystem
cthon: nfsv4
Starting BASIC tests: test directory /mnt/TMP (arg: -f)
./test1: File and directory creation test
created 6 files 6 directories 2 levels deep
./test1 ok.
./test2: File and directory removal test
removed 6 files 6 directories 2 levels deep
./test2 ok.
./test3: lookups across mount point
2 getcwd and stat calls
./test3 ok.
./test4: setattr, getattr, and lookup
20 chmods and stats on 10 files
./test4 ok.
./test5: read and write
wrote 1048576 byte file 1 times
read 1048576 byte file 1 times
./test5 ok.
./test6: readdir
202 entries read, 200 files
./test6 ok.
./test7: link and rename
./test7: (/mnt/TMP) newfile.1 has 1 links after link (expect 2) : No such file or directory
basic tests failed
cthon: nfsv3
Starting BASIC tests: test directory /mnt/TMP (arg: -f)
./test1: File and directory creation test
created 6 files 6 directories 2 levels deep
./test1 ok.
./test2: File and directory removal test
removed 6 files 6 directories 2 levels deep
./test2 ok.
./test3: lookups across mount point
2 getcwd and stat calls
./test3 ok.
./test4: setattr, getattr, and lookup
20 chmods and stats on 10 files
./test4 ok.
./test5: read and write
wrote 1048576 byte file 1 times
read 1048576 byte file 1 times
./test5 ok.
./test6: readdir
202 entries read, 200 files
./test6 ok.
./test7: link and rename
./test7: (/mnt/TMP) newfile.0 has 1 links after link (expect 2) : No such file or directory
basic tests failed
cthon: nfsv4/krb5
Starting BASIC tests: test directory /mnt/TMP (arg: -f)
./test1: File and directory creation test
created 6 files 6 directories 2 levels deep
./test1 ok.
./test2: File and directory removal test
removed 6 files 6 directories 2 levels deep
./test2 ok.
./test3: lookups across mount point
2 getcwd and stat calls
./test3 ok.
./test4: setattr, getattr, and lookup
20 chmods and stats on 10 files
./test4 ok.
./test5: read and write
wrote 1048576 byte file 1 times
read 1048576 byte file 1 times
./test5 ok.
./test6: readdir
202 entries read, 200 files
./test6 ok.
./test7: link and rename
./test7: (/mnt/TMP) newfile.1 has 1 links after link (expect 2) : No such file or directory
basic tests failed
cthon: nfsv3/krb5
Starting BASIC tests: test directory /mnt/TMP (arg: -f)
./test1: File and directory creation test
created 6 files 6 directories 2 levels deep
./test1 ok.
./test2: File and directory removal test
removed 6 files 6 directories 2 levels deep
./test2 ok.
./test3: lookups across mount point
2 getcwd and stat calls
./test3 ok.
./test4: setattr, getattr, and lookup
20 chmods and stats on 10 files
./test4 ok.
./test5: read and write
wrote 1048576 byte file 1 times
read 1048576 byte file 1 times
./test5 ok.
./test6: readdir
202 entries read, 200 files
./test6 ok.
./test7: link and rename
./test7: (/mnt/TMP) newfile.0 has 1 links after link (expect 2) : No such file or directory
basic tests failed
cthon: nfsv4/krb5i
Starting BASIC tests: test directory /mnt/TMP (arg: -f)
./test1: File and directory creation test
created 6 files 6 directories 2 levels deep
./test1 ok.
./test2: File and directory removal test
removed 6 files 6 directories 2 levels deep
./test2 ok.
./test3: lookups across mount point
2 getcwd and stat calls
./test3 ok.
./test4: setattr, getattr, and lookup
20 chmods and stats on 10 files
./test4 ok.
./test5: read and write
wrote 1048576 byte file 1 times
read 1048576 byte file 1 times
./test5 ok.
./test6: readdir
202 entries read, 200 files
./test6 ok.
./test7: link and rename
./test7: (/mnt/TMP) newfile.1 has 1 links after link (expect 2) : No such file or directory
basic tests failed
cthon: nfsv4/krb5p
Starting BASIC tests: test directory /mnt/TMP (arg: -f)
./test1: File and directory creation test
created 6 files 6 directories 2 levels deep
./test1 ok.
./test2: File and directory removal test
removed 6 files 6 directories 2 levels deep
./test2 ok.
./test3: lookups across mount point
2 getcwd and stat calls
./test3 ok.
./test4: setattr, getattr, and lookup
20 chmods and stats on 10 files
./test4 ok.
./test5: read and write
wrote 1048576 byte file 1 times
read 1048576 byte file 1 times
./test5 ok.
./test6: readdir
202 entries read, 200 files
./test6 ok.
./test7: link and rename
./test7: (/mnt/TMP) newfile.1 has 1 links after link (expect 2) : No such file or directory
basic tests failed
next reply other threads:[~2008-10-08 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 22:55 J. Bruce Fields [this message]
2008-10-09 2:03 ` connectathon test failures J. Bruce Fields
2008-10-09 2:10 ` J. Bruce Fields
2008-10-09 14:36 ` Trond Myklebust
2008-10-09 15:53 ` J. Bruce Fields
2008-10-09 17:36 ` Trond Myklebust
2008-10-09 19:23 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081008225543.GG14527@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond@netapp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox