Linux NFS development
 help / color / mirror / Atom feed
From: Omry Yadan <omry-FZzTFxfWWV5eoWH0uzbU5w@public.gmane.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org
Subject: Re: file open for write fails under stress
Date: Tue, 14 Oct 2008 15:49:53 +0200	[thread overview]
Message-ID: <48F4A381.4040700@yadan.net> (raw)
In-Reply-To: <1223990637.8907.3.camel@localhost>

Trond Myklebust wrote:

> On Tue, 2008-10-14 at 00:51 +0200, Omry Yadan wrote:
>   
>> 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.
>>     
>
> What version of nfs, filesystem on the server, export options, mount
> options,...?
>
>   

/etc/exports:
/var/vizi 38.99.126.160/28(rw,sync,no_subtree_check)
server file system : ext3 on a raid5 (900gb, 3x500gb hd).
server nfs version: 1.0.10

client mount:
nas1:/var/vizi on /var/vizi type nfs (rw,tcp,addr=38.99.126.163)


  reply	other threads:[~2008-10-14 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 22:51 file open for write fails under stress Omry Yadan
     [not found] ` <48F3D106.9020203-FZzTFxfWWV5eoWH0uzbU5w@public.gmane.org>
2008-10-14 13:23   ` Trond Myklebust
2008-10-14 13:49     ` Omry Yadan [this message]
     [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=48F4A381.4040700@yadan.net \
    --to=omry-fzztfxfwwv5eowh0uzbu5w@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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