From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 70121] Increasing efficiency of full data journaling
Date: Thu, 06 Mar 2014 05:28:19 +0000 [thread overview]
Message-ID: <bug-70121-13602-Vy8eJ3NxWe@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-70121-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=70121
--- Comment #4 from sworddragon2@aol.com ---
> It does no such thing.
What does it not?
> Data
> journaling only makes sense for an external journal on an ssd or
> similar
~2 years ago I have disabled full data journaling for a short time but at this
point an application crashed while it was writing a lot of files. The result
was that many files got damaged which encouraged me to never disable full data
journaling again. Now I'm seeing only 2 possible states of a file: Either it is
only registered in the filesystem with a size of 0 bytes or it is completely
written. I was never able to reproduce a half-written file with full data
journaling enabled.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-03-06 5:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 10:38 [Bug 70121] New: Increasing efficiency of full data journaling bugzilla-daemon
2014-02-07 11:28 ` [Bug 70121] " 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 [this message]
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-Vy8eJ3NxWe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.