From: Oleg Drokin <oleg.drokin@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Flush on file close
Date: Mon, 19 Apr 2010 18:31:49 -0400 [thread overview]
Message-ID: <AD12F5A3-D702-40CC-818F-CC477E3E90B1@oracle.com> (raw)
In-Reply-To: <201004192230.48196.andrew.perepechko@sun.com>
Hello!
On Apr 19, 2010, at 2:30 PM, Andrew Perepechko wrote:
> Since syncing may degrade performance to a large extent, what do you think is
> the best/most convenient/least intrusive way to switch to that behaviour?
> Should it be a mount option for the client or anything else?
Personally I think this is a non-issue for us.
There is no mad dash in other filesystems to implement this, aside from NFS where this
is what is guaranteed.
As long as we don't lose data after close (which we usually don't anyway) we are in the clear.
If we do (eviction, double failure) then there was some system exception that is kind of
similar to disk failure for regular fs.
Apps doing this "close after each write" should be fixed anyway because now they incur
additional overhead of two extra unneeded sync RPCs (open + close) and adding more overhead
to this is not going to help even if made optional.
Bye,
Oleg
next prev parent reply other threads:[~2010-04-19 22:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 18:30 [Lustre-devel] Flush on file close Andrew Perepechko
2010-04-19 22:31 ` Oleg Drokin [this message]
2010-04-20 2:34 ` Andreas Dilger
2010-04-20 5:16 ` Oleg Drokin
2010-04-20 7:56 ` Mitchell Erblich
2010-04-20 19:46 ` Oleg Drokin
2010-04-20 19:57 ` Oleg Drokin
2010-04-21 21:04 ` Andreas Dilger
2010-04-22 5:15 ` Alexey Lyashkov
2010-04-20 4:04 ` Andreas Dilger
2010-04-20 20:27 ` Nicolas Williams
2010-04-20 20:43 ` Nicolas Williams
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=AD12F5A3-D702-40CC-818F-CC477E3E90B1@oracle.com \
--to=oleg.drokin@oracle.com \
--cc=lustre-devel@lists.lustre.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 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.