From: Eric Sandeen <sandeen@sandeen.net>
To: "zhengbin.08747@h3c.com" <zhengbin.08747@h3c.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: hello, my xfs has a probelm. does anybody know this?thank you
Date: Tue, 25 Aug 2015 09:54:00 -0500 [thread overview]
Message-ID: <55DC8188.5060004@sandeen.net> (raw)
In-Reply-To: <7B5C2F2226F8AF419D625C6097AD814C5E26FE9C@H3CMLB12-EX.srv.huawei-3com.com>
On 8/25/15 4:08 AM, zhengbin.08747@h3c.com wrote:
> My OS is redhat7.1, the version of Linux kernel is “Linux version 3.10.0-229.el7.x86_64”
>
> Sometime xfs give a message like this
>
> Aug 11 15:51:05 localhost kernel: XFS (dm-4): metadata I/O error: block 0x7d9a010 ("xfs_trans_read_buf_map") error 117 numblks 16
> Aug 11 15:51:05 localhost kernel: XFS (dm-4): xfs_imap_to_bp: xfs_trans_read_buf() returned error 117.
> Aug 11 15:31:08 localhost kernel: XFS (dm-4): Metadata corruption detected at xfs_inode_buf_verify+0x75/0xd0 [xfs], block 0x7d9a010
> Aug 11 15:31:08 localhost kernel: XFS (dm-4): Unmount and run xfs_repair
Did you try running xfs_repair (or possibly better for the first run, do xfs_repair -n, to do a check-only run?)
> Aug 11 15:31:08 localhost kernel: XFS (dm-4): First 64 bytes of corrupted metadata buffer:
> Aug 11 15:31:08 localhost kernel: ffff88089144a000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> Aug 11 15:31:08 localhost kernel: ffff88089144a010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> Aug 11 15:31:08 localhost kernel: ffff88089144a020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> Aug 11 15:31:08 localhost kernel: ffff88089144a030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
So it seems to have read a completely zeroed-out block.
Isn't there a stack trace after this part of the message?
Hm I guess not; if you can hit it again, try
# sysctl -w fs.xfs.error_level=11
to turn up the error reporting level.
Any chance that this is a thinly provisioned device? Or what type of dm device is it?
> So is this a bug of xfs? or is the device’s error(the device actually did not save the data, but give xfs success message)?
Hard to say at this point.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-08-25 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 9:08 hello, my xfs has a probelm. does anybody know this?thank you zhengbin.08747
2015-08-25 14:54 ` Eric Sandeen [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=55DC8188.5060004@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=zhengbin.08747@h3c.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.