From: "J. R. Okajima" <hooanon05g@gmail.com>
To: trond.myklebust@primarydata.com, anna.schumaker@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: 4.8-rcN nfs O_DYSNC, write(2) doesn't return ENOSPC
Date: Sat, 03 Sep 2016 13:31:56 +0900 [thread overview]
Message-ID: <3647.1472877116@jrobl> (raw)
Hello NFS folks,
I am not subscribing this ML. Please CC to me explicitly when you reply.
I found a problem of NFS in linux-v4.8-rc[123]. Here is a reproducible
sequence.
- mount a rather small tmpfs, for example /tmp/srvr
- export it to localhost
- mount localhost:/tmp/srvr /tmp/clnt
- dd if=/dev/zero of=/tmp/clnt/full
After a while, dd ends with ENOSPC expectedly. But if I add "oflag=dsync"
to dd(1), it never ends. strace(1) shows dd repeats write(512bytes) and
gets the value 512.
If this is a known issue, please tell me the commit id of the fix.
J. R. Okajima
next reply other threads:[~2016-09-03 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 4:31 J. R. Okajima [this message]
2016-09-03 16:13 ` 4.8-rcN nfs O_DYSNC, write(2) doesn't return ENOSPC Trond Myklebust
2016-09-04 18:58 ` J. R. Okajima
2016-09-05 17:19 ` 4.8-rcN nfs, access(W_OK) on an immutable inode J. R. Okajima
2016-09-05 17:59 ` Trond Myklebust
2016-09-05 18:55 ` J. R. Okajima
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=3647.1472877116@jrobl \
--to=hooanon05g@gmail.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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.