From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12151] Unexplained fsck errors on a ext4 filesystem
Date: Fri, 1 May 2009 15:19:38 GMT [thread overview]
Message-ID: <200905011519.n41FJcBu021652@demeter.kernel.org> (raw)
In-Reply-To: <bug-12151-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12151
--- Comment #9 from Eric Sandeen <sandeen@redhat.com> 2009-05-01 15:19:38 ---
(In reply to comment #7)
> I have been running Fedora's kernels the whole time, and I haven't seen this
> issue with 2.6.29 kernels. I don't think I saw it with 2.6.28 kernels either. I
> wonder if Fedora has been putting more patches for ext4 in over what goes into
> Linus's tree.
Nathan - well, not really. I'll never put something in fedora that hasn't been
sent upstream, it's not how we work.
One difference may be that the 2.6.27 kernels in F10 did have the ext4 "stable"
backports that Ted was doing...
If you're running .29 kernels from fedora, it should be equivalent to what's
upstream. The only changes in F11 for example are:
Patch2920: linux-2.6-ext4-flush-on-close.patch
Patch2921: linux-2.6-ext4-really-print-warning-once.patch
--
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-01 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 21:38 [Bug 12151] New: Unexplained fsck errors on a ext4 filesystem bugme-daemon
2008-12-11 2:33 ` [Bug 12151] " bugme-daemon
2009-01-18 2:24 ` bugme-daemon
2009-01-18 21:30 ` bugme-daemon
2009-03-04 5:41 ` bugme-daemon
2009-03-04 5:43 ` bugme-daemon
2009-04-27 13:40 ` bugzilla-daemon
2009-04-30 9:10 ` bugzilla-daemon
2009-04-30 20:56 ` bugzilla-daemon
2009-05-01 13:52 ` bugzilla-daemon
2009-05-01 15:19 ` bugzilla-daemon [this message]
2009-05-02 16:29 ` bugzilla-daemon
2009-05-02 20:24 ` bugzilla-daemon
2009-05-02 22:14 ` 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=200905011519.n41FJcBu021652@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).