public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Simon Xu <xu.simon@oracle.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] dead loop of closing/removing tmp file when TMPDIR is on nfsv4
Date: Wed, 19 Sep 2012 11:55:41 +0800	[thread overview]
Message-ID: <5059423D.2090401@oracle.com> (raw)

Hi,

If nfsv4 filesystem is used for TMPDIR, some testcases will have dead 
loop when closing/removing tmp dir or file, and LTP output file will 
quickly reach several gigabytes in less than 10 seconds.

For example:

access02:

<<<test_output>>>
access02    1  TBROK  : chown(/mnt/nfsv4/ltp-7QMNLSoD0z/accsjrpxj, -1, 
0) failed: errno=EPERM(1): Operation not permitted
access02    2  TBROK  :  Remaining cases broken
access02    0  TWARN  :  tst_brk: Invalid Type: 4. Using TBROK
access02    3  TBROK  :  tmpdir_cleanup: no user cleanup function called 
before exiting
access02    4  TBROK  :  unexpected signal 11 received (pid = 6283).
access02    5  TFAIL  :  close(test_file2) failed: errno=EBADF(9): Bad 
file descriptor
access02    6  TFAIL  :  close(temp_file) failed: errno=EBADF(9): Bad 
file descriptor
access02    7  TFAIL  :  close(temp_file) failed: errno=EBADF(9): Bad 
file descriptor
access02    8  TFAIL  :  close(temp_file) failed: errno=EBADF(9): Bad 
file descriptor
access02    9  TFAIL  :  close(temp_file) failed: errno=EBADF(9): Bad 
file descriptor
access02   10  TFAIL  :  close(temp_file) failed: errno=EBADF(9): Bad 
file descriptor
access02   11  TFAIL  :  close(temp_file) failed: errno=EBADF(9): Bad 
file descriptor
access02   12  TFAIL  :  close(temp_file) failed: errno=EBADF(9): Bad 
file descriptor
access02   13  TFAIL  :  close(temp_file) failed: errno=EBADF(9): Bad 
file descriptor
access02   14  TFAIL  :  close(temp_file) failed: errno=EBADF(9): Bad 
file descriptor
access02   15  TFAIL  :  close(temp_file) failed: errno=EBADF(9): Bad 
file descriptor
.....
.....

access01:

access01    0  TWARN  :  tst_rmdir: 
rmobj(/mnt/nfsv4/ltp-pGpmqg8e6y/acc8wRrm5) failed: 
lstat(/mnt/nfsv4/ltp-pGpmqg8e6y/acc8wRrm5) failed; errno=2: No such file 
or directory
access01    0  TWARN  :  tst_brk: Invalid Type: 4. Using TBROK
access01 6621  TBROK  :  tmpdir_cleanup: no user cleanup function called 
before exiting
access01    0  TWARN  :  tst_rmdir: 
rmobj(/mnt/nfsv4/ltp-pGpmqg8e6y/acc8wRrm5) failed: 
lstat(/mnt/nfsv4/ltp-pGpmqg8e6y/acc8wRrm5) failed; errno=2: No such file 
or directory
access01    0  TWARN  :  tst_brk: Invalid Type: 4. Using TBROK
access01 6622  TBROK  :  tmpdir_cleanup: no user cleanup function called 
before exiting
access01    0  TWARN  :  tst_rmdir: 
rmobj(/mnt/nfsv4/ltp-pGpmqg8e6y/acc8wRrm5) failed: 
lstat(/mnt/nfsv4/ltp-pGpmqg8e6y/acc8wRrm5) failed; errno=2: No such file 
or directory
access01    0  TWARN  :  tst_brk: Invalid Type: 4. Using TBROK
access01 6623  TBROK  :  tmpdir_cleanup: no user cleanup function called 
before exiting
......
......

nfs mount option: (rw,vers=4,addr=192.168.1.15,clientaddr=192.168.1.137)
My first guess is that this has something to do with nfs silly 
renaming.  Any idea?

Thanks
Simon

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

                 reply	other threads:[~2012-09-19  3:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5059423D.2090401@oracle.com \
    --to=xu.simon@oracle.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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