From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13292] ext4 without journal reproductible file corruption
Date: Thu, 28 May 2009 21:16:10 GMT [thread overview]
Message-ID: <200905282116.n4SLGAbh003298@demeter.kernel.org> (raw)
In-Reply-To: <bug-13292-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13292
--- Comment #7 from Frank Mayhar <fmayhar@google.com> 2009-05-28 21:16:09 ---
Yesterday I pulled down Ted's ext4-stable tree and built it. Today I used it
to actually reproduce this problem. Now to try to track it down...
BTW, my suspicion is that the problem is either somewhere in the rest of the
kernel or maybe some post-2.6.26 change elsewhere is tickling a problem in ext4
itself. I suspect this because we're very nearly up-to-date with ext4 itself
(modulo some patches that don't seem directly relevant to this issue) but the
rest of our kernel is still pretty much straight 2.6.26. If it were strictly
an ext4 issue I would think we would be able to reproduce it with our kernel,
but we can't.
I'm going to work on tracking it down; I'm posting here just to make sure I'm
not duplicating someone else's effort. Ted?
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-05-28 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 9:22 [Bug 13292] New: ext4 without journal reproductible file corruption bugzilla-daemon
2009-05-13 23:10 ` [Bug 13292] " bugzilla-daemon
2009-05-14 14:14 ` bugzilla-daemon
2009-05-14 20:07 ` bugzilla-daemon
2009-05-20 1:02 ` bugzilla-daemon
2009-05-20 17:36 ` bugzilla-daemon
2009-05-27 19:23 ` bugzilla-daemon
2009-05-28 21:16 ` bugzilla-daemon [this message]
2009-07-21 9:02 ` 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=200905282116.n4SLGAbh003298@demeter.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).