From: NeilBrown <neilb-IBi9RG/b67k@public.gmane.org>
To: wharms-fPG8STNUNVg@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC PATCH manpages] write.2, fsync.2, close.2: update description of error codes
Date: Fri, 15 Sep 2017 08:36:56 +1000 [thread overview]
Message-ID: <87ingk9abb.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <59BA36C5.9000506-fPG8STNUNVg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
On Thu, Sep 14 2017, walter harms wrote:
> Am 14.09.2017 01:50, schrieb NeilBrown:
>>
>> Since 4.13, errors from writeback are more reliably reported
>> to all file descriptors that might be relevant.
>>
>> Add notes to this effect, and also add details about ENOSPC and EDQUOT
>> which can be delayed in a similar manner to EIO - for NFS in particular.
>>
>
> I never read EDQUOT before but it is real:
>
> see:
> http://elixir.free-electrons.com/linux/latest/source/security/keys/request_key.c
>
> -EDQUOT
> * if insufficient key quota was available to create a new key
EDQUOT existed long before security keys.
It's original purpose is to report Disk QUOTa problems. If you write to
a file and you have exhausted you quota, you get EDQUOT.
http://elixir.free-electrons.com/linux/latest/source/fs/quota/dquot.c#L1318
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-09-14 22:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170720194227.7830-1-jlayton@kernel.org>
[not found] ` <1503683981.22608.0.camel@redhat.com>
[not found] ` <87h8wsiog4.fsf@notabene.neil.brown.name>
[not found] ` <1503920855.4563.12.camel@redhat.com>
[not found] ` <87pobfgo9q.fsf@notabene.neil.brown.name>
[not found] ` <1504004058.4679.7.camel@redhat.com>
[not found] ` <87efrjb2mn.fsf@notabene.neil.brown.name>
[not found] ` <1504784132.4954.12.camel@redhat.com>
[not found] ` <1504796087.3561.7.camel@primarydata.com>
[not found] ` <874ls9diij.fsf@notabene.neil.brown.name>
[not found] ` <1505126785.4916.7.camel@redhat.com>
[not found] ` <87poawc390.fsf@notabene.neil.brown.name>
[not found] ` <1505229616.28831.26.camel@redhat.com>
[not found] ` <87efrbbne1.fsf@notabene.neil.brown.name>
[not found] ` <1505305391.4822.13.camel@redhat.com>
2017-09-13 23:50 ` [RFC PATCH manpages] write.2, fsync.2, close.2: update description of error codes NeilBrown
[not found] ` <87ingm9n04.fsf-wvvUuzkyo1HefUI2i7LXDhCRmIWqnp/j@public.gmane.org>
2017-09-14 7:59 ` walter harms
[not found] ` <59BA36C5.9000506-fPG8STNUNVg@public.gmane.org>
2017-09-14 22:36 ` NeilBrown [this message]
2017-09-14 10:48 ` Jeff Layton
2017-09-15 7:50 ` Michael Kerrisk (man-pages)
[not found] ` <28da8888-e8f9-31d5-a3dd-d3c2a5e9037a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-15 8:25 ` NeilBrown
[not found] ` <1505386139.4870.10.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-09-28 3:01 ` NeilBrown
[not found] ` <87fub75xxr.fsf-wvvUuzkyo1HefUI2i7LXDhCRmIWqnp/j@public.gmane.org>
2017-09-28 12:20 ` Jeff Layton
2017-09-28 16:19 ` Michael Kerrisk (man-opages)
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=87ingk9abb.fsf@notabene.neil.brown.name \
--to=neilb-ibi9rg/b67k@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wharms-fPG8STNUNVg@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).