DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=FU+3zqnXWCgSJ1ALViGKX6UQdsfgzBroL8LXEdnFq56D6EsrHE54kw0FWA1cDN1MkO
         sI5xk9AStqNTnOMGrKA1bMn+ij2u8rBn5cgcE8ZNWYjZsBt2EbJpOLbLivorbHYjWHhA
         65FIWLl2iUx2QUuEHroyNgoxYP+uJGWT5S8yA=
MIME-Version: 1.0
Date: Mon, 29 Nov 2010 13:37:17 +0100
Message-ID: <AANLkTing7+SK+pavFehR4AGDbRRfFwvvzNxgWQ3zRp+O@mail.gmail.com>
Subject: Atomic non-durable file write API
From: Olaf van der Spek <olafvdspek@gmail.com>
To: linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 784
Lines: 21

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/