Messages in this thread | | | Date | Mon, 6 Dec 2010 09:03:23 -0800 | From | Randy Dunlap <> | Subject | Re: Atomic non-durable file write API |
| |
On Mon, 6 Dec 2010 17:45:23 +0100 Olaf van der Spek wrote:
> On Mon, Nov 29, 2010 at 1:37 PM, Olaf van der Spek <olafvdspek@gmail.com> wrote: > > Hi, > > > > Since the introduction of ext4, some apps/users have had issues with > > file corruption after a system crash. It's not a bug in the FS AFAIK > > and it's not exclusive to ext4. > > Writing a temp file, fsync, rename is often proposed. However, the > > durable aspect of fsync isn't always required and this way has other > > issues. > > What is the recommended way for atomic non-durable (complete) file writes? > > > > I'm also wondering why FSs commit after open/truncate but before > > write/close. AFAIK this isn't necessary and thus suboptimal. > > Somebody? > --
maybe try linux-fsdevel@vger.kernel.org or linux-ext4@vger.kernel.org mailing lists?
--- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code ***
| |