linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf van der Spek <olafvdspek@gmail.com>
To: Nick Piggin <npiggin@gmail.com>
Cc: "Ted Ts'o" <tytso@mit.edu>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-ext4@vger.kernel.org
Subject: Re: Atomic non-durable file write API
Date: Sat, 25 Dec 2010 16:24:22 +0100	[thread overview]
Message-ID: <AANLkTinjtoF0gOdi6TV+RPjMkeqA8fcrkJBYRBd5WQ==@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikHMZDyNkaOux5VWUHvC5D1cXHEFKxhvzfVjN+Q@mail.gmail.com>

On Sat, Dec 25, 2010 at 12:33 PM, Nick Piggin <npiggin@gmail.com> wrote:
>> It's not just about dpkg, I'm still very interested in answers to my
>> original questions.
>
> Arbitrary atomic but non-durable file write operation?

No, not arbitrary writes. It's about complete file writes.
Also, don't forget my question about how to preserve meta-data
including file owner.

> That's significantly
> different to how any part of the pagecache or filesystem or syscall API
> is set up. Writes are not atomic, and syncs are only for durability (not
> atomicity), atomicity is typically built on top of these durable points.
>
> That is quite fundamental functionality and suits simple
> implementations of filesystems and writeback caches.
>
> If you start building complex atomicity semantics, then you get APIs

Atomic semantics are not (that) complex.

> which can't be supported by all filesystems, Linux specific, adds
> complexity from the API through to the pagecache and to the
> filesystems, and is Linux specific.

> Compare that to using cross platform, mature and well tested sqlite
> or bdb, how much reason do we have for implementing such APIs?

Like I said before, it's not about DB-like functionality but about
complete file writes/updates. For example, I've got a file in an
editor and I want to save it.

> It's not that it isn't possible, it's that there is no way we're adding
> such a thing unless it really helps and is going to be widely used.
>
> What exact use case do you have in mind, and what exact API
> semantics do you want, anyway?

Let me copy the original post:
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, like losing file meta-data.
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.

Olaf

  reply	other threads:[~2010-12-25 15:24 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTing7+SK+pavFehR4AGDbRRfFwvvzNxgWQ3zRp+O@mail.gmail.com>
2010-12-09 12:03 ` Atomic non-durable file write API Olaf van der Spek
2010-12-16 12:22   ` Olaf van der Spek
2010-12-16 20:11     ` Ric Wheeler
2010-12-18 22:15       ` Calvin Walton
2010-12-19 16:39         ` Olaf van der Spek
2010-12-23 15:49           ` Olaf van der Spek
2010-12-23 21:51             ` Neil Brown
2010-12-23 22:22               ` Ted Ts'o
     [not found]                 ` <4D13E98D.8070105@ontolinux.com>
     [not found]                   ` <20101224004825.GF12763@thunk.org>
     [not found]                     ` <4D13F09D.4010703@ontolinux.com>
     [not found]                       ` <20101224095105.GG12763@thunk.org>
2010-12-24 11:14                         ` Olaf van der Spek
2010-12-25  3:15                           ` Ted Ts'o
2010-12-25 10:41                             ` Olaf van der Spek
2010-12-25 11:33                               ` Nick Piggin
2010-12-25 15:24                                 ` Olaf van der Spek [this message]
2010-12-25 17:25                                   ` Nick Piggin
2010-12-26 15:08                                     ` Olaf van der Spek
2010-12-26 15:55                                       ` Boaz Harrosh
2010-12-26 16:02                                         ` Olaf van der Spek
2010-12-26 16:27                                           ` Boaz Harrosh
2010-12-26 18:26                                             ` Olaf van der Spek
2010-12-26 16:43                                       ` Nick Piggin
2010-12-26 18:51                                         ` Olaf van der Spek
2010-12-26 22:10                                           ` Ted Ts'o
2010-12-27  0:30                                             ` Christian Stroetmann
2010-12-27  1:04                                               ` Ted Ts'o
2010-12-27  1:30                                                 ` Christian Stroetmann
2010-12-27  2:53                                                   ` Ted Ts'o
2010-12-27 10:21                                             ` Olaf van der Spek
2010-12-27 11:07                                               ` Marco Stornelli
2010-12-27 15:30                                               ` Christian Stroetmann
2010-12-27 19:07                                                 ` Olaf van der Spek
2010-12-27 19:30                                                   ` Christian Stroetmann
2010-12-28 17:22                                                     ` Olaf van der Spek
2010-12-28 20:59                                                       ` Neil Brown
2010-12-28 22:00                                                         ` Greg Freemyer
2010-12-28 22:06                                                           ` Olaf van der Spek
2010-12-28 22:15                                                             ` Greg Freemyer
2010-12-28 22:28                                                               ` Olaf van der Spek
2010-12-28 22:35                                                               ` Neil Brown
2010-12-29 11:05                                                           ` Dave Chinner
2010-12-28 22:10                                                         ` Olaf van der Spek
2010-12-28 22:31                                                           ` Neil Brown
2010-12-28 22:54                                                             ` Olaf van der Spek
2010-12-28 23:42                                                               ` Ted Ts'o
2010-12-29  9:09                                                                 ` Olaf van der Spek
2010-12-29 15:30                                                               ` Christian Stroetmann
2010-12-29 15:41                                                                 ` Olaf van der Spek
2010-12-29 16:30                                                                   ` Christian Stroetmann
2010-12-29 17:14                                                                     ` Olaf van der Spek
2010-12-30  0:50                                                                       ` Neil Brown
2011-01-07 14:23                                                                         ` Olaf van der Spek
2010-12-27  4:12                                           ` Nick Piggin
2010-12-27 11:48                                             ` Olaf van der Spek
2010-12-27 12:43                                               ` Olaf van der Spek
2010-12-28  0:45                                               ` Ted Ts'o
2010-12-24 11:17               ` Olaf van der Spek
2010-12-25 21:40                 ` Neil Brown
2010-12-23 22:43             ` Dave Chinner
2010-12-23 22:47               ` Ted Ts'o
2010-12-26  9:59                 ` Amir Goldstein
2010-12-26 15:23                   ` Olaf van der Spek
2010-12-26 16:52                     ` Nick Piggin

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='AANLkTinjtoF0gOdi6TV+RPjMkeqA8fcrkJBYRBd5WQ==@mail.gmail.com' \
    --to=olafvdspek@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).