All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Neil Brown <neilb@suse.de>, nfs@lists.sourceforge.net
Subject: Re: [PATCH/RFC] Return ENOSPC and EDQUOT for nfs writes	earlier.
Date: Fri, 13 Jul 2007 13:16:34 -0400	[thread overview]
Message-ID: <4697B372.4080003@oracle.com> (raw)
In-Reply-To: <1184272296.30876.159.camel@heimdal.trondhjem.org>

[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]

Trond Myklebust wrote:
> On Thu, 2007-07-12 at 10:12 +1000, Neil Brown wrote:
>> When a write to a local filesystem hits a space limitation such as
>> filesystem-full or quota-exhausted, the write fails synchronously.
>> You get ENOSPC or EDQUOT immediately.
>>
>> NFS cannot do that efficiently.
>>
>> Currently, you don't get these errors until 'fsync' or 'close'.  That
>> is very different from local filesystem behaviour, and is less than
>> ideal.
>>
>> The following patch causes these two errors to be returned through the
>> next write call once they are known about.
>>
>> A possible extension would be to set a flag when we first get such an
>> error, clear it when a write succeeds, and while the flag is set, do
>> all writes synchronously.  This would be even closer to
>> local-filesystem semantics, but I'm not sure it is worth it.
> 
> Well... I've been thinking along these last lines myself (i.e. forcing
> all subsequent writes to be synchronous whenever an error occurs).

OK, but...

After it is triggered by a write error, how would the synchronous 
behavior be turned off?  Both EDQUOT and ENOSPC, for example, are really 
a temporary error; if applications are smart enough, they can retry an 
EDQUOT and might get a successful write.  In that case, performance 
would be hosed until.... the client decides it's OK to use unstable 
writes again.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 315 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
email;internet:chuck dot lever at nospam oracle dot com
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2007-07-13 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  0:12 [PATCH/RFC] Return ENOSPC and EDQUOT for nfs writes earlier Neil Brown
2007-07-12 20:31 ` Trond Myklebust
2007-07-13  0:01   ` Neil Brown
2007-07-13 17:16   ` Chuck Lever [this message]
2007-07-13 21:12     ` Trond Myklebust

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=4697B372.4080003@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --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 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.