From: Christoph Hellwig <hch@infradead.org>
To: linux-xfs@vger.kernel.org
Subject: slab corruption in generic/388
Date: Wed, 20 Sep 2017 07:57:40 -0700 [thread overview]
Message-ID: <20170920145740.GA9685@infradead.org> (raw)
Recently I've a few of these warnings in generic/388 with a 4k
filesystem on x86_64, v5 file system with reflink and rmap
enabled but otherwise defaults. If someones got and idea where
this might be from I'm curious, otherwise I'll add it to my TODO list.
[ 5062.894006] XFS (sdb): xfs_do_force_shutdown(0x1) called from line 236 of file fs/xfs/libxfs/xfs_defer.c. Return address = 0xffffffff8156cb46
[ 5062.908923] XFS (sdb): xfs_imap_to_bp: xfs_trans_read_buf() returned error -5.
[ 5062.986682] XFS (sdb): Unmounting Filesystem
[ 5063.008740] XFS (sdb): EXPERIMENTAL reverse mapping btree feature enabled. Use at your own risk!
[ 5063.010063] XFS (sdb): EXPERIMENTAL reflink feature enabled. Use at your own risk!
[ 5063.011543] XFS (sdb): Mounting V5 Filesystem
[ 5063.299537] XFS (sdb): Starting recovery (logdev: internal)
[ 5063.305221] XFS (sdb): Ending recovery (logdev: internal)
[ 5063.355721] Slab corruption (Tainted: G W ): xfs_rui_item start=ffff88003908f708, len=672
[ 5063.357058] Redzone: 0x9f911029d74e35b/0x9f911029d74e35b
[ 5063.357842] Last user: [<ffffffff815dfa2c>](xfs_rui_item_free+0x1c/0x30)
[ 5063.358712] 080: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b jkkkkkkkkkkkkkkk
[ 5063.359813] Single bit error detected. Probably bad RAM.
[ 5063.360512] Run memtest86+ or a similar memory test tool.
[ 5063.361216] Prev obj: start=ffff88003908f450, len=672
[ 5063.361876] Redzone: 0x9f911029d74e35b/0x9f911029d74e35b
[ 5063.362836] Last user: [<ffffffff815dfa2c>](xfs_rui_item_free+0x1c/0x30)
[ 5063.363704] 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
[ 5063.364708] 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
[ 5063.365729] Next obj: start=ffff88003908f9c0, len=672
[ 5063.366397] Redzone: 0x9f911029d74e35b/0x9f911029d74e35b
[ 5063.367101] Last user: [<ffffffff815dfa2c>](xfs_rui_item_free+0x1c/0x30)
[ 5063.367846] 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
[ 5063.368637] 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
[ 5065.460847] XFS (sdb): Unmounting Filesystem
next reply other threads:[~2017-09-20 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 14:57 Christoph Hellwig [this message]
2017-09-20 19:37 ` slab corruption in generic/388 Darrick J. Wong
2017-09-21 13:25 ` Chandan Rajendra
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=20170920145740.GA9685@infradead.org \
--to=hch@infradead.org \
--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 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.