All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: XFS corruptions
Date: Thu, 10 Dec 2015 10:46:24 -0600	[thread overview]
Message-ID: <5669AC60.1070709@sandeen.net> (raw)
In-Reply-To: <558408F298C8CE4C89D93BD56AB474E8018617B2B3@EXBE1IS02.omnifone.com>

On 11/30/15 10:51 AM, 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.
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Does that mean it finds and fixes something "temporarily?"  If so, what?

-Eric

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

  parent reply	other threads:[~2015-12-10 16:46 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
2015-12-10 16:46 ` Eric Sandeen [this message]
  -- 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=5669AC60.1070709@sandeen.net \
    --to=sandeen@sandeen.net \
    --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.