From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 70121] Increasing efficiency of full data journaling
Date: Fri, 07 Mar 2014 15:42:13 +0000 [thread overview]
Message-ID: <bug-70121-13602-v2ZpdxuZ92@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 #8 from sworddragon2@aol.com ---
Thanks for the information :)
In this case full data journaling seems not to make all the things I thought it
does. Maybe my last tests are just too long ago. But this means also that I
still can have data loss if the system crashes while writing to the disk. It
would be really nice if the filesystem would provide such a mechanism in the
future.
> How does the file system know that the file has "successfully been
> written"?
Does the filesystem really not know if the file is complete? If this could be
achieved a transaction safety should be not the problem here.
> If you think it can be done, plesae submit patches. :-)
Sure I would if:
- My experience with C would be a little higher.
- Or at least if I would have the time to make a deeper look into the
sourcecode and the coding rules for the kernel.
I have posted the last few years many hundred bugs/feature requests in ~100
different projects and am still doing this many times a week. But don't worry,
they don't have so many bogus reports as I'm reporting here :)
The kernel is really a difficult place if you are not directly involved with it
but want to improve something. But some of my tickets here had already success.
Also I'm programming on own projects and this all together consumes much time.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-03-07 15:42 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
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 [this message]
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-v2ZpdxuZ92@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).