From: Dave Chinner <david@fromorbit.com>
To: Roy Zhang <royzhangzzl@gmail.com>
Cc: xfs-masters <xfs-masters@oss.sgi.com>, xfs <xfs@oss.sgi.com>
Subject: Re: [xfs-masters] xfs corruption - structure need cleaning
Date: Wed, 16 Oct 2013 12:46:54 +1100 [thread overview]
Message-ID: <20131016014654.GC4446@dastard> (raw)
In-Reply-To: <CAMg3XqptephuOPEJ-iiQF+Bs5Kp7MO=D-siw6fbNMG4=2CQGKg@mail.gmail.com>
On Wed, Oct 16, 2013 at 08:12:00AM +0800, Roy Zhang wrote:
> Hi Dave,
> I performance a ssd and hdd by flashcache. The info as below.
> kernel version 2.6.32.220
So you're using out of tree modules in the IO path, on a custom
Centos 6.3 kernel and you are getting random hangs waiting for IO
completion.
FWIW, 15,000 lines of log files is not the information I asked for,
but this:
[1535047.183083] MEMBlaze Hardware IO Request Irresponsible
indicates that you are using some kind of PCIe flash hardware from a
chinese startup that doesn't have in-kernel drivers or english
documentation. There's no way we can really help you diagnose IO
stack problems given these conditions.
FWIW, your logs indicate that something is going wrong in your IO
stack, not with XFS. XFS is triggering the hung task timer waiting
for IO completion, and only after many, many reboots as a result of
these hangs you see a log corruption when trying to mount the
filesystem.
So - look to flashcache or your hardware as the source of your
problem...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-10-16 1:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 13:45 xfs corruption - structure need cleaning Roy Zhang
2013-10-15 13:54 ` Carlos Maiolino
2013-10-15 20:43 ` [xfs-masters] " Dave Chinner
[not found] ` <CAMg3XqptephuOPEJ-iiQF+Bs5Kp7MO=D-siw6fbNMG4=2CQGKg@mail.gmail.com>
2013-10-16 1:46 ` Dave Chinner [this message]
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=20131016014654.GC4446@dastard \
--to=david@fromorbit.com \
--cc=royzhangzzl@gmail.com \
--cc=xfs-masters@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox