All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omry Yadan <omry-FZzTFxfWWV5eoWH0uzbU5w@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: file open for write fails under stress
Date: Tue, 14 Oct 2008 00:51:50 +0200	[thread overview]
Message-ID: <48F3D106.9020203@yadan.net> (raw)

I have an application that open many files for writing very fast, in a
way - it can almost be looked as a file system stress test.


my application is single threaded, and I noticed the following problem
when running a single instance of it:


at some point, after opening (and closing) many files for writing, the
application fails to open a file for writing.

if I sleep for 1 second and try again, it works.


my NFS server runs Debian etch 32 bit, with

nfs-kernel-server and nfs-common (1:1.0.10-6+etch.1).


client is also etch 32.

kernel on both is :2.6.18-6-686 #1 SMP Tue Jun 17 21:31:27 UTC 2008 i686


both machines are quad core.



I tried to mount with tcp and udp, and tried both sync and async export
point.


is this a known issue?

any known workaround that will not require messing up the application
with retry logic?


    Omry.


             reply	other threads:[~2008-10-13 23:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 22:51 Omry Yadan [this message]
     [not found] ` <48F3D106.9020203-FZzTFxfWWV5eoWH0uzbU5w@public.gmane.org>
2008-10-14 13:23   ` file open for write fails under stress Trond Myklebust
2008-10-14 13:49     ` Omry Yadan
     [not found]       ` <48F4A381.4040700-FZzTFxfWWV5eoWH0uzbU5w@public.gmane.org>
2008-10-14 14:10         ` Trond Myklebust
2008-10-14 14:46           ` Omry Yadan
2008-10-14 17:10   ` J. Bruce Fields
2008-10-14 17:59     ` Omry Yadan

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=48F3D106.9020203@yadan.net \
    --to=omry-fzztfxfwwv5eowh0uzbu5w@public.gmane.org \
    --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.