linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 70121] New: Increasing efficiency of full data journaling
Date: Thu, 06 Feb 2014 10:38:04 +0000	[thread overview]
Message-ID: <bug-70121-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=70121

            Bug ID: 70121
           Summary: Increasing efficiency of full data journaling
           Product: File System
           Version: 2.5
    Kernel Version: 3.13.1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: sworddragon2@aol.com
        Regression: No

Full data journaling provides the ability that it is guaranteed that a file
will never be saved visible for the user in a damaged state (except a hardware
defect appears afterwards). But this has the disadvantage that the writing
througput is ~halfed as all files are written 2 times.

Here comes the idea: From a logical view to achieve this safety it is not
needed to write the file 2 times. A simple committing should achieve the same
level of safety. Here is an example: The filesystem could store a value for the
file which is reflecting its state. It is initialized as empty value indicating
the file has not successfully be written. As soon as the file has been written
it is set to 1. This would avoid writing the file 2 times and still guarantee
that the file will never be visible for te user in a damaged state on a crash
as the filesystem check would see that the file state is unequal to 1 and
correct the problem.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2014-02-06 10:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 10:38 bugzilla-daemon [this message]
2014-02-07 11:28 ` [Bug 70121] Increasing efficiency of full data journaling bugzilla-daemon
2014-02-07 14:49 ` bugzilla-daemon
2014-03-05 20:37 ` [Bug 70121] New: " Phillip Susi
2014-03-05 21:48 ` [Bug 70121] " bugzilla-daemon
2014-03-06  5:28 ` bugzilla-daemon
2014-03-07 20:41   ` Phillip Susi
2014-03-06 15:34 ` bugzilla-daemon
2014-03-07  7:16 ` bugzilla-daemon
2014-03-07 13:48   ` Theodore Ts'o
2014-03-07 13:48 ` bugzilla-daemon
2014-03-07 15:42 ` bugzilla-daemon
2014-03-07 20:41 ` bugzilla-daemon

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=bug-70121-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /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).