public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vaughan" <cxt9401@163.com>
To: linux-xfs@vger.kernel.org
Subject: How to get disk-location from "metadata I/O error"?
Date: Mon, 18 Dec 2017 19:16:33 +0800	[thread overview]
Message-ID: <002e01d377f1$a986be00$fc943a00$@163.com> (raw)

Hi All,


I encounter the following output from time to time. Since xfs is built on
our own virtual disk, it's more likely that our vdisk is buggy.
Can anyone tell me how to figure out the on-disk location given the block
number? Does it follow the following formula?
On-disk location = <block number from metadata I/O error> * <bsize of data
section of xfs_info>
However, the result from the above formula suggests the metadata is out of
range of my disk, confused...

Another question is the corrupted metadata buffer always start with 8 bytes
of '8' character. Does xfs use '8' as any magic label?
I'm using centos-7.2, kernel 3.10.0-327.el7.


XFS (md_d27): Metadata corruption detected at xfs_agf_read_verify+0x70/0x120
[xfs], block 0x1e8ffa08
XFS (md_d27): Unmount and run xfs_repair
XFS (md_d27): First 64 bytes of corrupted metadata buffer:
ffff88042fc69000: 38 38 38 38 38 38 38 38 00 00 00 00 00 00 00 00
88888888........
ffff88042fc69010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
ffff88042fc69020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
ffff88042fc69030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
XFS (md_d27): metadata I/O error: block 0x1e8ffa08
("xfs_trans_read_buf_map") error 117 numblks 8
XFS (md_d27): page discard on page ffffea000b34f900, inode 0x23e, offset
362840064.
XFS (md_d27): Metadata corruption detected at xfs_agf_read_verify+0x70/0x120
[xfs], block 0x1e8ffa08
XFS (md_d27): Unmount and run xfs_repair

# xfs_info /mnt/md/27
meta-data=/dev/md_d27            isize=256    agcount=32, agsize=10682336
blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=0        finobt=0
data     =                       bsize=4096   blocks=341834752, imaxpct=5
         =                       sunit=32     swidth=64 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal               bsize=4096   blocks=166911, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

#cat /proc/partition
253     1728 1367342592 md_d27


-Vaughan


             reply	other threads:[~2017-12-18 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 11:16 Vaughan [this message]
2017-12-18 15:41 ` How to get disk-location from "metadata I/O error"? Carlos Maiolino
2017-12-18 21:41   ` 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='002e01d377f1$a986be00$fc943a00$@163.com' \
    --to=cxt9401@163.com \
    --cc=linux-xfs@vger.kernel.org \
    /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