From: "Darrick J. Wong" <djwong@kernel.org>
To: guodf <15147193722@163.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Metadata CRC error detected at xfs_bmbt block 0x1868f56bb0/0x1000
Date: Wed, 16 Mar 2022 20:08:47 -0700 [thread overview]
Message-ID: <20220317030847.GZ8224@magnolia> (raw)
In-Reply-To: <16d2444c.2cc8.17f95b788b9.Coremail.15147193722@163.com>
On Thu, Mar 17, 2022 at 10:31:47AM +0800, guodf wrote:
>
>
> Hello:
> A fatal error occurred in the XFS file system of my production environment when I run the following command
> error：
> [root@localhost 0316]# xfs_metadump -g -o -w /dev/centos/home xfs.img
> Metadata CRC error detected at xfs_agf block 0x187ffffe79/0x200
> xfs_metadump: cannot init perag data (-74). Continuing anyway.
> Copying free space trees of AG 10
> Metadata CRC error detected at xfs_bmbt block 0x1868f56bb0/0x1000
>
>
> xfs_metadump: invalid numrecs (65079) in bmapbtd block 48/220114342
> Copying free space trees of AG 22 Metadata CRC error detected at xfs_bmbt block 0x18a6ffeb38/0x1000
>
>
> xfs_metadump: invalid numrecs (39031) in bmapbtd block 49/81788312
> Metadata CRC error detected at xfs_bmbt block 0x19a1ffeda8/0x1000
> xfs_metadump: invalid numrecs (49606) in bmapbtd block 51/71302632
> Metadata CRC error detected at xfs_bmbt block 0x1a9cfff018/0x1000
> xfs_metadump: invalid numrecs (4194) in bmapbtd block 53/60816952
> Copying free space trees of AG 48 bad magic number
>
>
> xfs_metadump: cannot read superblock for ag 49
> Metadata CRC error detected at xfs_agi block 0x187ffffe7a/0x200
> Metadata CRC error detected at xfs_agfl block 0x187ffffe7b/0x200
> /usr/sbin/xfs_metadump: line 33: 6369 Segmentation fault (core dumped) xfs_db$DBOPTS -i -p xfs_metadump -c "metadump$OPTS $2" $1
>
>
> I have two questions and hope to get your reply
> 1：Metadata CRC error detected at xfs_agfl block 0x187ffffe7b/0x200
>
> What does the red font mean？What does it mean？
There are checksum errors in the metadata, which implies that something
weird happened with the storage (bitflips in the cable, torn writes,
broken disk firmware)...
> 2：How can I fix it
Send us a coredump and the xfs_db binary so we can try to fix this
crash, and run xfs_repair?
--D
>
>
> Thank you very much
>
prev parent reply other threads:[~2022-03-17 3:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 2:31 Metadata CRC error detected at xfs_bmbt block 0x1868f56bb0/0x1000 guodf
2022-03-17 3:08 ` Darrick J. Wong [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=20220317030847.GZ8224@magnolia \
--to=djwong@kernel.org \
--cc=15147193722@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