From: Dave Chinner <david@fromorbit.com>
To: DS <xfs@bob.dscon.sk>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: is the flush-on-close-after-truncate still needed?
Date: Fri, 27 Jun 2008 17:28:00 +1000 [thread overview]
Message-ID: <20080627072800.GA29319@disturbed> (raw)
In-Reply-To: <20080627071312.GB15920@bob.dscon.sk>
On Fri, Jun 27, 2008 at 09:13:12AM +0200, DS wrote:
> Thanx for interest.
>
> There is no chance to change all scripts (too many customers and
> thousands and thousands perl/php skripts).
>
> I think it isn't right way compiling own perl/php libs with needed changes on
> open/fopen function.
Overwriting files by truncating then first and then not fsync'ing
the file is a sure way to lose data if the system crashes. That's
an application bug, not a filesystem bug, because the filesystem is
only doing what it is told to do. XFS is ensuring that lazy
application writers are unlikely to lose data when they carelessly
overwriting data.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2008-06-27 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 17:09 is the flush-on-close-after-truncate still needed? Eric Sandeen
2008-06-18 17:49 ` Dave Chinner
2008-06-18 17:59 ` Eric Sandeen
2008-06-26 21:09 ` DS
2008-06-26 21:19 ` Eric Sandeen
2008-06-26 21:24 ` Eric Sandeen
2008-06-27 7:13 ` DS
2008-06-27 7:28 ` Dave Chinner [this message]
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=20080627072800.GA29319@disturbed \
--to=david@fromorbit.com \
--cc=sandeen@sandeen.net \
--cc=xfs@bob.dscon.sk \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox