| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: fsync, rename, O_ATOMIC/O_PONIES |
| From: | Olaf van der Spek <olaf@xxxxxxxx> |
| Date: | Fri, 02 Mar 2012 13:39:37 +0100 |
| User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] xfstests: before test execution, print test number to syslog, Stefan Behrens |
|---|---|
| Next by Date: | [XFS] xfs_repair time how long it takes??, Ryan Lee |
| Previous by Thread: | [PATCH] xfstests: before test execution, print test number to syslog, Stefan Behrens |
| Next by Thread: | Re: fsync, rename, O_ATOMIC/O_PONIES, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |