From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: NFSv3 list <linux-nfs@vger.kernel.org>
Subject: Connectathon locking test fails over NFSv3 with EBUSY
Date: Tue, 22 Jun 2010 15:03:03 -0400 [thread overview]
Message-ID: <4C2108E7.6040909@oracle.com> (raw)
It looks like the connectathon tests race with the removal of deleted
files. The actual lock test is successful, but when the scripts attempt
to reset the test directory for another pass, the RMDIR fails because
the directory is full of ".nfsxxx" files.
Seems like RMDIR should wait for those silly deletes before trying to
remove the parent directory.
I've seen this with both 2.6.34 and 2.6.35-rc3 clients, and it happens
nearly every time.
Test #15 - Test 2nd open and I/O after lock and close.
Parent: Second open succeeded.
Parent: 15.0 - F_LOCK [ 0, ENDING] PASSED.
Parent: 15.1 - F_ULOCK [ 0, ENDING] PASSED.
Parent: Closed testfile.
Parent: Wrote 'abcdefghij' to testfile [ 0, 11 ].
Parent: Read 'abcdefghij' from testfile [ 0, 11 ].
Parent: 15.2 - COMPARE [ 0, b] PASSED.
** PARENT pass 1 results: 49/49 pass, 1/1 warn, 0/0 fail (pass/total).
** CHILD pass 1 results: 64/64 pass, 0/0 warn, 0/0 fail (pass/total).
Congratulations, you passed the locking tests!
... Pass 2 ...
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000d8e00000041': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000df100000050': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000dfb0000004a': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000dec00000047': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000df90000004b': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000dfa0000004e': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000df80000004f': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000df20000004c': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000deb00000051': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000def00000048': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000dea0000004d': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000de900000049': Device or
resource busy
Starting BASIC tests: test directory /mnt/klimt/ellison.test (arg: -t)
mkdir: cannot create directory `/mnt/klimt/ellison.test': File exists
./test1: File and directory creation test
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000d8e00000041': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000df100000050': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000dfb0000004a': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000dec00000047': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000df90000004b': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000dfa0000004e': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000df80000004f': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000df20000004c': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000deb00000051': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000def00000048': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000dea0000004d': Device or
resource busy
rm: cannot remove
`/mnt/klimt/ellison.test/.nfs0000000000000de900000049': Device or
resource busy
./test1: (/home/cel/src/cthon04/basic) can't remove old test directory
/mnt/klimt/ellison.test
basic tests failed
Tests failed, leaving /mnt/klimt mounted
[cel@ellison cthon04]$
--
Chuck Lever
next reply other threads:[~2010-06-22 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 19:03 Chuck Lever [this message]
2010-06-22 19:17 ` Connectathon locking test fails over NFSv3 with EBUSY Trond Myklebust
2010-06-23 17:51 ` Chuck Lever
2010-06-23 18:06 ` Staubach_Peter
[not found] ` <BF3BB6D12298F54B89C8DCC1E4073D80017545B4-1Zg0zMUlrbd9m/dOYFj4Yjjd7nCn89gW@public.gmane.org>
2010-06-23 18:43 ` Trond Myklebust
2010-06-23 19:17 ` Chuck Lever
2010-06-23 19:26 ` Trond Myklebust
[not found] ` <1277321217.4991.64.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-06-23 19:55 ` Chuck Lever
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=4C2108E7.6040909@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.