From: Aaron Straus <aaron@merfinllc.com>
To: chucklever@gmail.com
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Hans-Peter Jansen <hpj@urpla.net>,
linux-kernel@vger.kernel.org, Neil Brown <neilb@suse.de>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [NFS] blocks of zeros (NULLs) in NFS files in kernels >= 2.6.20
Date: Mon, 22 Sep 2008 10:37:15 -0700 [thread overview]
Message-ID: <20080922173715.GE12483@merfinllc.com> (raw)
In-Reply-To: <76bd70e30809221026g7bde774pbffa35881682ea4b@mail.gmail.com>
Hi,
On Sep 22 01:26 PM, Chuck Lever wrote:
> Why can't you use O_SYNC | O_APPEND ?
In our case, some of the writers are not in our control. Another case
we see the issue is you spawn a job:
job 1> out 2> err &
tail -f out err
--
Also, we actually do like caching the writes (b/c log files do not need
to be checked immediately after being written). We just wish the cache
could be written out in-order.
If there's no way to make that happen... we can reorganize our
file-system, exports, mounts, etc so that the log file directory is
mounted with the sync option.
However, the problem *might* be annoying and wide-spread enough to
warrant a change.
Anyway, thanks!
Regards,
=a=
--
===================
Aaron Straus
aaron@merfinllc.com
next prev parent reply other threads:[~2008-09-22 17:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 19:19 blocks of zeros (NULLs) in NFS files in kernels >= 2.6.20 Aaron Straus
2008-09-05 19:56 ` [NFS] " Chuck Lever
2008-09-05 20:04 ` Aaron Straus
2008-09-05 20:36 ` Bernd Eckenfels
2008-09-05 20:36 ` Chuck Lever
2008-09-05 22:14 ` Aaron Straus
2008-09-06 0:03 ` Aaron Straus
2008-09-08 19:02 ` Aaron Straus
2008-09-08 21:15 ` Chuck Lever
2008-09-08 22:02 ` Aaron Straus
2008-09-09 19:46 ` Aaron Straus
2008-09-11 16:55 ` Chuck Lever
2008-09-11 17:19 ` Aaron Straus
2008-09-11 17:48 ` Chuck Lever
2008-09-11 18:49 ` Aaron Straus
2008-09-22 16:05 ` Hans-Peter Jansen
2008-09-22 16:35 ` Trond Myklebust
2008-09-22 17:04 ` Aaron Straus
2008-09-22 17:26 ` Chuck Lever
2008-09-22 17:37 ` Aaron Straus [this message]
2008-09-22 17:29 ` Trond Myklebust
2008-09-22 17:45 ` Aaron Straus
2008-09-22 18:43 ` Aaron Straus
2008-09-22 18:45 ` Hans-Peter Jansen
2008-09-22 18:45 ` Hans-Peter Jansen
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=20080922173715.GE12483@merfinllc.com \
--to=aaron@merfinllc.com \
--cc=chucklever@gmail.com \
--cc=hpj@urpla.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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