* Atomic non-durable file write API
@ 2010-11-29 12:37 Olaf van der Spek
2010-12-01 10:27 ` Olaf van der Spek
2010-12-06 16:45 ` Olaf van der Spek
0 siblings, 2 replies; 4+ messages in thread
From: Olaf van der Spek @ 2010-11-29 12:37 UTC (permalink / raw)
To: linux-kernel
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.
Greetings,
Olaf
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Atomic non-durable file write API
2010-11-29 12:37 Atomic non-durable file write API Olaf van der Spek
@ 2010-12-01 10:27 ` Olaf van der Spek
2010-12-06 16:45 ` Olaf van der Spek
1 sibling, 0 replies; 4+ messages in thread
From: Olaf van der Spek @ 2010-12-01 10:27 UTC (permalink / raw)
To: linux-kernel
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.
Is this the wrong list for this kind of question?
Greetings,
Olaf
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Atomic non-durable file write API
2010-11-29 12:37 Atomic non-durable file write API Olaf van der Spek
2010-12-01 10:27 ` Olaf van der Spek
@ 2010-12-06 16:45 ` Olaf van der Spek
2010-12-06 17:03 ` Randy Dunlap
1 sibling, 1 reply; 4+ messages in thread
From: Olaf van der Spek @ 2010-12-06 16:45 UTC (permalink / raw)
To: linux-kernel
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?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Atomic non-durable file write API
2010-12-06 16:45 ` Olaf van der Spek
@ 2010-12-06 17:03 ` Randy Dunlap
0 siblings, 0 replies; 4+ messages in thread
From: Randy Dunlap @ 2010-12-06 17:03 UTC (permalink / raw)
To: Olaf van der Spek; +Cc: linux-kernel
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 ***
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-12-06 17:03 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-11-29 12:37 Atomic non-durable file write API Olaf van der Spek
2010-12-01 10:27 ` Olaf van der Spek
2010-12-06 16:45 ` Olaf van der Spek
2010-12-06 17:03 ` Randy Dunlap
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).