From: Eric Sandeen <sandeen@sandeen.net>
To: Hieu Le Trung <hieult@Cybersoft-VN.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_force_shutdown
Date: Tue, 13 Oct 2009 09:51:42 -0500 [thread overview]
Message-ID: <4AD493FE.6000403@sandeen.net> (raw)
In-Reply-To: <CEBA5E865263FA4D8848D53D92E6A9AE0416AB0B@DAKLAK.cybersoft-vn.com>
Hieu Le Trung wrote:
> Eric Sandeen wrote:
>> Hieu Le Trung wrote:
>>> Hi,
>>>
>>> What may cause metadata becomes bad? I got xfs_force_shutdown with
> 0x2
>>> parameter.
>> Software bugs or hardware problems. If you provide the actual kernel
>> message we can offer more info on what xfs saw and why it shut down.
>
> I'm not sure which one is it but the issue is hard to reproduce.
> I have following in the dmesg but I'm not sure it's the right one
> <1>I/O error in filesystem ("sda2") meta-data dev sda2 block 0xf054f4
> ("xlog_iodone") error 5 buf count 32768
Were there IO errors from the storage before this? i.e. did some lower
layer go bad.
> <5>xfs_force_shutdown(sda2,0x2) called from line 956 of file
> fs/xfs/xfs_log.c. Return address = 0x801288d8
>
> Furthermore, the driver's write cache is
> <5>SCSI device sda: drive cache: write back
That's fine...
> The xfs_logprint shows 'Bad log record header'
> xfs_logprint: /dev/sda2 contains a mounted and writable filesystem
> data device: 0x802
> log device: 0x802 daddr: 15735648 length: 20480
>
> Header 0xa4 wanted 0xfeedbabe
> **********************************************************************
> * ERROR: header cycle=164 block=14634 *
> **********************************************************************
> Bad log record header
>
> So I wonder what may cause bad record header?
Probably the IO errors when attempting to write to the log ...
>>> How can I analyze the metadata dump file?
>> the metadump file is just the metadata skeleton of the filesystem; you
>> can mount it, repair it, point xfs_db at it to debug it, etc.
>
> Is there any tutorials or guideline in using xfs_db to debug the issue?
xfs_db has a manpage, but I'm not sure the answer will be found by using
it. It will only look at what data made it to the disk, and you had an
IO error.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-10-13 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 10:29 xfs_force_shutdown Hieu Le Trung
2009-10-12 13:23 ` xfs_force_shutdown Eric Sandeen
2009-10-13 8:43 ` xfs_force_shutdown Hieu Le Trung
2009-10-13 14:51 ` Eric Sandeen [this message]
2009-10-13 15:15 ` xfs_force_shutdown Hieu Le Trung
2009-10-13 15:31 ` xfs_force_shutdown Eric Sandeen
2009-10-13 15:39 ` xfs_force_shutdown Hieu Le Trung
2009-10-13 15:48 ` xfs_force_shutdown Eric Sandeen
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=4AD493FE.6000403@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hieult@Cybersoft-VN.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.