From: "Libor Klepáč" <libor.klepac@bcom.cz>
To: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: BUG: Metadata corruption detected at xfs_attr3_leaf_read_verify
Date: Fri, 21 Oct 2016 12:46:21 +0000 [thread overview]
Message-ID: <3764770.FZr9v1sA2Y@libor-nb> (raw)
Hello,
last week we have started to have problems with one virtual machine running debian jessie, with kernel 3.16.7-ckt20-1+deb8u4.
There are some logs,
I don't have complete logs, but filesystem shutdown twice with
Oct 14 12:00:24 bajkonur2 kernel: [18872956.205316] XFS (dm-2): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd5/0xe0 [xfs], block 0x12f63f40
Oct 14 12:00:24 bajkonur2 kernel: [18872956.208382] XFS (dm-2): Unmount and run xfs_repair
Oct 14 12:00:24 bajkonur2 kernel: [18872956.209385] XFS (dm-2): First 64 bytes of corrupted metadata buffer:
Oct 14 12:00:24 bajkonur2 kernel: [18872956.210187] ffff88011dadd000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 ................
Oct 14 12:00:24 bajkonur2 kernel: [18872956.211816] ffff88011dadd010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 ..... ..........
Oct 14 12:00:24 bajkonur2 kernel: [18872956.213390] ffff88011dadd020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Oct 14 12:00:24 bajkonur2 kernel: [18872956.214983] ffff88011dadd030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Oct 14 12:00:24 bajkonur2 kernel: [18872956.216598] XFS (dm-2): xfs_do_force_shutdown(0x8) called from line 1330 of file /build/linux-U7H2aZ/linux-3.16.7-ckt20/fs/xfs/xfs_buf.c. Return address = 0xffffffffa03ef820
Oct 14 12:00:24 bajkonur2 kernel: [18872956.217448] XFS (dm-2): Corruption of in-memory data detected. Shutting down filesystem
Oct 14 12:00:24 bajkonur2 kernel: [18872956.218338] XFS (dm-2): Please umount the filesystem and rectify the problem(s)
next reply other threads:[~2016-10-21 13:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 12:46 Libor Klepáč [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-21 17:09 BUG: Metadata corruption detected at xfs_attr3_leaf_read_verify Libor Klepáč
2016-10-21 17:59 ` Brian Foster
2016-10-21 22:20 ` Dave Chinner
2016-10-23 6:48 ` Libor Klepáč
2016-10-24 2:40 ` Dave Chinner
2016-10-25 6:52 ` Libor Klepáč
2016-10-31 8:54 ` Libor Klepáč
2016-10-31 11:57 ` Brian Foster
2016-10-31 12:02 ` Dave Chinner
2016-10-31 15:36 ` Libor Klepáč
2016-11-08 11:09 ` Libor Klepáč
2016-11-08 11:28 ` Libor Klepáč
2016-11-10 5:29 ` Dave Chinner
[not found] ` <2152865.L3K5Xz7SXO@libor-nb>
2016-11-10 21:30 ` Dave Chinner
2016-11-23 11:40 ` Libor Klepáč
2016-11-26 6:05 ` Eric Sandeen
2016-12-06 9:08 ` Libor Klepáč
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=3764770.FZr9v1sA2Y@libor-nb \
--to=libor.klepac@bcom.cz \
--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;
as well as URLs for NNTP newsgroup(s).