From: Dave Chinner <david@fromorbit.com>
To: Vlad Bespalov <vlad.botanic@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: possible null pointer in xlog_iodone
Date: Tue, 18 Jun 2013 10:19:20 +1000 [thread overview]
Message-ID: <20130618001920.GM29376@dastard> (raw)
In-Reply-To: <CA+aXbB5b0Vqp9mTPUiV4x_bGkVfbnCTErW-QoX=SMjv0mADf-w@mail.gmail.com>
On Mon, Jun 17, 2013 at 06:38:56PM +0400, Vlad Bespalov wrote:
> CentOS 6.4 kernel 2.6.32-358.2.1.el6.x86_64
> i`ll try to make a script that can be used out-of-house.
>
> several requests may have failed (un)conveniently, so we have passed
> through setting XLOG_IO_ERROR in xfs_log_force_unmount() and
> eventually skipped xlog_wait altogether:
> -----------------
> <1>XFS (<device>): metadata I/O error: block 0xa03e1d ("xlog_iodone")
> error 5 buf count 1024
> <5>XFS (<device>): xfs_do_force_shutdown(0x2) called from line 1052 of
> file fs/xfs/xfs_log.c. Return address = 0xffffffffa0559e51
> <1>XFS (<device>): Log I/O Error Detected. Shutting down filesystem
> <1>XFS (<device>): Please umount the filesystem and rectify the problem(s)
> <4>XFS (<device>): xfs_log_force: error 5 returned.
> <5>XFS (<device>): xfs_do_force_shutdown(0x1) called from line 1063 of
> file fs/xfs/linux-2.6/xfs_buf.c. Return address = 0xffffffffa0575
> <4>XFS (<device>): xfs_log_force: error 5 returned.
> <4>XFS (<device>): xfs_log_force: error 5 returned.
> ...
> <1>XFS (mtab~): metadata I/O error: block 0xa03e1b ("xlog_iodone")
> error 5 buf count 1024
And the rest of dmesg showing the stack trace of the oops?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-06-18 0:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 17:15 possible null pointer in xlog_iodone Vlad Bespalov
2013-06-14 19:42 ` Mark Tinguely
2013-06-15 1:03 ` Dave Chinner
2013-06-17 14:38 ` Vlad Bespalov
2013-06-18 0:19 ` Dave Chinner [this message]
2013-06-18 0:37 ` Vlad Bespalov
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=20130618001920.GM29376@dastard \
--to=david@fromorbit.com \
--cc=vlad.botanic@gmail.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.