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 13292] ext4 without journal reproductible file corruption
Date: Thu, 14 May 2009 20:07:25 GMT	[thread overview]
Message-ID: <200905142007.n4EK7PX5029724@demeter.kernel.org> (raw)
In-Reply-To: <bug-13292-13602@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=13292





--- Comment #3 from Frank Mayhar <fmayhar@google.com>  2009-05-14 20:07:25 ---
Thank you for the very detailed information you provided.  Unfortunately I
can't reproduce this problem in my environment.  That environment is, however,
somewhat different from yours, in that it's a 2.6.26 kernel plus ext4 patches
up to March 16 (minus a few patches that depended on changes in other parts of
the kernel).

My suggestion is that you drop back to the March 16 (or so) kernel and see if
you can reproduce the problem.  If you can't reproduce it then you can do a
binary search to see where the problem started, i.e. try an April 15 kernel,
etc., until you home in on the offending commit.

If you _can_ reproduce the problem with the March 16 kernel then something more
complex is going on and I'll have to try again to reproduce it here.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2009-05-14 20:07 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 [this message]
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
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=200905142007.n4EK7PX5029724@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).