From: Edward Roper <eroper@wanfear.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "Lever, Charles" <Charles.Lever@netapp.com>,
neilb@cse.unsw.edu.au, nfs@lists.sourceforge.net
Subject: Re: close() / nfs commit performance
Date: 01 Jul 2003 12:40:26 -0700 [thread overview]
Message-ID: <1057088426.26307.0.camel@themachine.sanera.net> (raw)
In-Reply-To: <shshe67xeyd.fsf@charged.uio.no>
So in theory running nfs async is no more dangerous than using a local
app that calls close() without fsync()?
On Mon, 2003-06-30 at 17:34, Trond Myklebust wrote:
> >>>>> " " == Edward Roper <eroper@wanfear.com> writes:
>
> > Perhaps local close() calls don't actually commit to disk?
>
> man 2 close
> (and read the NOTES)
>
> and then
>
> man 2 fsync
>
> Cheers,
> Trond
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-07-01 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 22:39 close() / nfs commit performance Lever, Charles
2003-06-30 23:18 ` Edward Roper
2003-07-01 0:34 ` Trond Myklebust
2003-07-01 19:40 ` Edward Roper [this message]
2003-07-06 21:30 ` Tom McNeal
2003-07-01 19:55 ` Edward Roper
2003-07-01 21:36 ` Edward Roper
-- strict thread matches above, loose matches on Subject: below --
2003-06-30 20:28 Edward Roper
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=1057088426.26307.0.camel@themachine.sanera.net \
--to=eroper@wanfear.com \
--cc=Charles.Lever@netapp.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--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 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.