From: Greg Banks <gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
To: nfs-Uh4cUGhLB8SgSpxsJD1C4w@public.gmane.org
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFSERR_NOSPC nfs-client bug
Date: Tue, 18 Mar 2008 12:43:56 +1100 [thread overview]
Message-ID: <47DF1E5C.9090607@melbourne.sgi.com> (raw)
In-Reply-To: <200803172021.08327.nfs-Uh4cUGhLB8SgSpxsJD1C4w@public.gmane.org>
Ray Ferguson wrote:
> I've discovered a bug in the linux nfs client. Specifically it ignores
> NFSERR_NOSPC messages (code 28) from an NFS server and happily continues
> pounding it with data.
>
It doesn't ignore ENOSPC, it reports it on close(). Of course this is
often several gigabytes of lost data too late.
Sensible clients (e.g. Irix) store that error on the inode and report it
on the next call to write().
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
The cake is *not* a lie.
I don't speak for SGI.
next prev parent reply other threads:[~2008-03-18 1:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 1:21 NFSERR_NOSPC nfs-client bug Ray Ferguson
[not found] ` <200803172021.08327.nfs-Uh4cUGhLB8SgSpxsJD1C4w@public.gmane.org>
2008-03-18 1:43 ` Greg Banks [this message]
[not found] ` <47DF1E5C.9090607-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-03-18 1:50 ` Ray Ferguson
[not found] ` <200803172050.22223.nfs-Uh4cUGhLB8SgSpxsJD1C4w@public.gmane.org>
2008-03-18 2:08 ` Greg Banks
[not found] ` <47DF2415.6070802-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-03-18 3:09 ` Trond Myklebust
[not found] ` <1205809775.22258.9.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-03-18 4:03 ` Greg Banks
[not found] ` <47DF3F01.9050504-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-03-18 6:08 ` NeilBrown
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=47DF1E5C.9090607@melbourne.sgi.com \
--to=gnb-cp1dwlodopni96+mszhfpqc/g2k4zdhf@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfs-Uh4cUGhLB8SgSpxsJD1C4w@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 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.