linux-ext4 - [Bug 70121] Increasing efficiency of full data journaling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-70121-13602-Vy8eJ3NxWe@https.bugzilla.kernel.org/>
Date:	Thu, 06 Mar 2014 05:28:19 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 70121] Increasing efficiency of full data journaling

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

--- Comment #4 from sworddragon2@....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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html