linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ted Ts'o" <tytso@mit.edu>
To: Nanakos Chrysostomos <nanakos@wired-net.gr>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Ext4 Kernel Crash
Date: Mon, 30 Jan 2012 12:26:59 -0500	[thread overview]
Message-ID: <20120130172659.GA7681@thunk.org> (raw)
In-Reply-To: <20120129175057.GA4699@dinofilaria.home>

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

  parent reply	other threads:[~2012-01-30 17:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2012-02-26 12:18 Nanakos Chrysostomos

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=20120130172659.GA7681@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nanakos@wired-net.gr \
    /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).