All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Sandeep Patel <spatel@omnifone.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS corruptions
Date: Mon, 30 Nov 2015 14:04:23 -0800	[thread overview]
Message-ID: <20151130220423.GA16277@birch.djwong.org> (raw)
In-Reply-To: <20151130215112.GM26718@dastard>

On Tue, Dec 01, 2015 at 08:51:12AM +1100, Dave Chinner wrote:
> On Mon, Nov 30, 2015 at 04:51:57PM +0000, Sandeep Patel wrote:
> > Hi,
> > 
> > We have multiple 22 disk raid 6 arrays using LSI 9280-24i4e raid
> > cards, all using enterprise grade drives. The array is setup with
> > physical drive cache disabled and mounted using inode64 with
> > nobarriers option in Oracle Linux Server release 6.6, kernel
> > version 3.8.13-55.1.5.el6uek.x86_64. We are suffering from
> > corruptions with xfs_repair unable to permanently fix the the
> > issues. Output of dmesg from the latest corruption.
> > 
> > Pid: 5319, comm: glusterfsd Not tainted 3.8.13-55.1.5.el6uek.x86_64 #2
> 
> FYI, we cannot really support vendor enterprise on the upstream lists
> because the code base is so different from vanilla/upstream kernels.
> I same exactly the same thing for bugs reported on RHEL/CentOS
> kernels, and for SLES kernels - only the vendor can properly support
> their own franken-kernels...
>
> Hence I'd suggest that you report the problem to your Oracle support
> contact so they can walk you through the process of finding the
> problem....
> 
> [ Darrick is really going to thank me for saying this. ]

Probably what I'd have written anyway. :)

Oracle support might just tell you to upgrade the kernel whatever the
latest is.  3.8.13-55 is pretty far back AFAIK.

(Is not a support engineer, nor do I play one on TV.)

--D

> 
> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-11-30 22:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 16:51 XFS corruptions Sandeep Patel
2015-11-30 17:40 ` Emmanuel Florac
2015-11-30 18:06   ` Sandeep Patel
2015-11-30 18:45     ` Emmanuel Florac
2015-12-01 12:18       ` Sandeep Patel
2015-12-01 13:50         ` Emmanuel Florac
2015-12-01 14:01           ` Sandeep Patel
2015-12-10 15:07           ` Sandeep Patel
2015-12-10 15:46             ` Emmanuel Florac
2015-12-10 19:51               ` Sandeep Patel
2016-01-11 14:20               ` Sandeep Patel
2016-01-11 15:16                 ` Emmanuel Florac
2016-03-16 13:15                   ` Sandeep Patel
2016-03-16 14:07                     ` Emmanuel Florac
2015-11-30 21:51 ` Dave Chinner
2015-11-30 22:04   ` Darrick J. Wong [this message]
2015-12-10 16:46 ` Eric Sandeen
  -- strict thread matches above, loose matches on Subject: below --
2008-09-04 17:11 xfs corruptions Bernd Schubert
2008-09-04 23:02 ` Dave Chinner

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=20151130220423.GA16277@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=spatel@omnifone.com \
    --cc=xfs@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.