mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Newall <david@davidnewall.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Guilherme Vilela <vilela.list@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Problem to recognize that the file system is full
Date: Fri, 07 Sep 2007 06:28:33 +0930	[thread overview]
Message-ID: <46E069F9.2040700@davidnewall.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709061445290.25942@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Sep 4 2007 13:53, Guilherme Vilela wrote:
>   
>> I'm tryng to mount a nfs file system with the option async and run a
>> program that writes to the file system. The problem is that the
>> program keep writing even when the file system is full.
>>     
>
> man 5 exports
>
>    async  This option allows the NFS server to violate  the  NFS  protocol
>           and  reply  to  requests before any changes made by that request
>           have been committed to stable storage (e.g. disc drive).
>   

(That means it's a feature.)

>> This program does'nt occur when mounting with the sync
>> option or with async and noac option, but the performance get very
>> poor and that is important to my application. The problem doesnt occur
>> too with the local file system. I'm running linux centos 5.0.
>>     
>
> About ac/localhost, I am not really sure what makes it work.
man 5 nfs

   noac Disable attribute caching, and force synchronous writes.  This
        extracts a server performance penalty but it allows two different
        NFS clients to get reasonable good results when both clients are
        actively writing to common filesystem on the server.


      reply	other threads:[~2007-09-06 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <89a10cbc0709040951u1786e7e3g76708bfcb7117f44@mail.gmail.com>
2007-09-04 16:53 ` Guilherme Vilela
2007-09-06 12:48   ` Jan Engelhardt
2007-09-06 20:58     ` David Newall [this message]

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=46E069F9.2040700@davidnewall.com \
    --to=david@davidnewall.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vilela.list@gmail.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

all inboxes | Powered by JetHome®