From: Ben Greear <greearb@candelatech.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Bug with O_DIRECT in 2.6.36-rc3?
Date: Fri, 03 Sep 2010 11:58:28 -0700 [thread overview]
Message-ID: <4C814554.1000800@candelatech.com> (raw)
I was getting ENOMEM errors on write when using O_DIRECT in 2.6.36-rc3 plus the
patch I just posted for srcaddr= (my test harness needs that feature to work).
It seems to work fine w/out O_DIRECT enabled.
The same patch against 2.6.34.6 works fine with and without O_DIRECT.
After the ENOMEM, I cannot un-mount, even with -f (says it's busy).
But, fuser doesn't show any users.
Anyone tried O_DIRECT recently?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2010-09-03 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 18:58 Ben Greear [this message]
2010-09-07 18:41 ` Bug with O_DIRECT in 2.6.36-rc3? Ben Greear
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=4C814554.1000800@candelatech.com \
--to=greearb@candelatech.com \
--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