From: Olaf van der Spek <olaf@xwis.net>
To: xfs@oss.sgi.com
Subject: Re: fsync, rename, O_ATOMIC/O_PONIES
Date: Fri, 02 Mar 2012 13:39:37 +0100 [thread overview]
Message-ID: <4F50BF89.7020909@xwis.net> (raw)
Hi XFS devs,
I'm a bit late to the party, but I'd like to respond to some comments at
http://lwn.net/Articles/476263/#Comments
http://lwn.net/Articles/484709/
> Could any of the fsync advocates post real code that does the atomic
variant of open, write, close?
> Hint: it's not possible without tons of regressions.
> Linux devs should really provide a proper solution (like O_ATOMIC)
instead of blaming app devs for not doing the impossible.
I'd like to ask:
- Is there a tool to log all unsafe operations?
- What is the *right* way to update a file?
I've asked the last question multiple times, but nobody has been able to
give me a proper answer.
Greetings,
Olaf
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-03-02 12:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:39 Olaf van der Spek [this message]
2012-03-02 13:12 ` fsync, rename, O_ATOMIC/O_PONIES Christoph Hellwig
2012-03-04 17:14 ` Olaf van der Spek
2012-03-05 1:02 ` Dave Chinner
2012-03-05 15:44 ` Olaf van der Spek
2012-03-05 23:17 ` Dave Chinner
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=4F50BF89.7020909@xwis.net \
--to=olaf@xwis.net \
--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