From: Nanakos Chrysostomos <nanakos@wired-net.gr>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Ext4 Kernel Crash
Date: Sun, 26 Feb 2012 14:18:02 +0200 [thread overview]
Message-ID: <20120226121802.GA8600@dinofilaria.home> (raw)
Hi Ted,
I tried a newer kernel and for the moment there are no problems.
I am testing our systems this weekend and the new week. I will
let you know the results.
Kind regards,
Chris
On Mon, Jan 30, 2012 at 12:26:59PM -0500, Ted Ts'o wrote:
> On Sun, Jan 29, 2012 at 07:50:57PM +0200, Nanakos Chrysostomos wrote:
> > Dear Linux Kernel Developers,
> > I am writing to report a kernel or ext4 bug.
>
> Hi Nanakos,
>
> My apologies for not responding to the message that you sent to me
> personally three days ago, but I was on vacation in Hawaii; the best
> place to send queries about ext4 file systems is to use the
> linux-ext4@vger.kernel.org mailing list.
>
> One thing that I would immediately suggest is to see whether you can
> reproduce this bug using a modern kernel. You are currently using a
> RHEL6-derived kernel (2.6.32-220.4.1.el6.x86_64). The ext4 file
> system in such a kernel is quite different from what is in upstream,
> and there were a large number of bugs that have been fixed in ext4
> since 2.6.32. Many of these fixes were backported into the RHEL6
> kernel, but I'm not an expert on which fixes have been backported into
> RHEL6 and which haven't. (Especially since Red Hat doesn't release
> broken-out patches for their RHEL kernels....)
>
> My understanding is that Gluster doesn't require any kernel-side
> patches, so it should be OK to run Gluster on a v3.2 kernel.
> Alternatively, if you are a paid customer of RHEL6, I'd suggest
> sending a support request to Red Hat.
>
> Best regards,
>
> - Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2012-02-26 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 12:18 Nanakos Chrysostomos [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-29 17:50 Ext4 Kernel Crash Nanakos Chrysostomos
2012-01-29 22:03 ` Jesper Juhl
2012-01-31 8:34 ` Nanakos V. Chrysostomos
2012-01-30 17:26 ` Ted Ts'o
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=20120226121802.GA8600@dinofilaria.home \
--to=nanakos@wired-net.gr \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).