From: DENIEL Philippe <philippe.deniel@cea.fr>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: How does the client manage NFS3ERR_NOSPC ?
Date: Mon, 05 Mar 2012 18:16:32 +0100 [thread overview]
Message-ID: <4F54F4F0.108@cea.fr> (raw)
Hi List,
I ran a stupid test (using the kernel's knfsd) : I filled up completely
a filesystem with a few big file. When it was 100% full (no free block
at all), I ran a dd on it.
The dd said it could write 793 blocks of size 1mb and failed on IO
error. At the end, I could see an empty file in the NFS exported tree.
Question is :
- why did I get EIO and not ENOSPC ?
- why did dd say "hey, I could write 793 blocks" when it wrote
nothing (and could not write anything).
Do you have an idea on that ?
Regards
Philippe
next reply other threads:[~2012-03-05 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 17:16 DENIEL Philippe [this message]
2012-03-05 21:01 ` How does the client manage NFS3ERR_NOSPC ? Myklebust, Trond
2012-03-05 21:42 ` Malahal Naineni
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=4F54F4F0.108@cea.fr \
--to=philippe.deniel@cea.fr \
--cc=linux-nfs@vger.kernel.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).