lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 07 Sep 2007 06:28:33 +0930
From:	David Newall <david@...idnewall.com>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
CC:	Guilherme Vilela <vilela.list@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Problem to recognize that the file system is full

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ