From: "Libor Klepáč" <libor.klepac@bcom.cz>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs_repair: junk leaf attribute if count == 0
Date: Wed, 24 May 2017 11:18:47 +0000 [thread overview]
Message-ID: <4648960.1DrcVCcZxK@libor-nb> (raw)
In-Reply-To: <b6492357-4bf3-c570-be33-90010e3b1967@sandeen.net>
Hi,
after quiet two months , another crash, trace is same as before.
There are no XFS lines before this, kern.log goes back to 23. april.
May 24 12:05:12 vps2 kernel: [3729926.243353] XFS (dm-2): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xe8/0x100 [xfs], xfs_attr3_leaf block 0x171c60c0
May 24 12:05:12 vps2 kernel: [3729926.247586] XFS (dm-2): Unmount and run xfs_repair
May 24 12:05:12 vps2 kernel: [3729926.249022] XFS (dm-2): First 64 bytes of corrupted metadata buffer:
May 24 12:05:12 vps2 kernel: [3729926.250424] ffff9fbb1d73a000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 ................
May 24 12:05:12 vps2 kernel: [3729926.251870] ffff9fbb1d73a010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 ..... ..........
May 24 12:05:12 vps2 kernel: [3729926.253412] ffff9fbb1d73a020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 24 12:05:12 vps2 kernel: [3729926.254941] ffff9fbb1d73a030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
May 24 12:05:12 vps2 kernel: [3729926.256478] CPU: 1 PID: 454 Comm: xfsaild/dm-2 Tainted: G E 4.9.0-0.bpo.2-amd64 #1 Debian 4.9.13-1~bpo8+1
May 24 12:05:12 vps2 kernel: [3729926.256480] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/14/2014
May 24 12:05:12 vps2 kernel: [3729926.256483] 0000000000000000 ffffffffb1329cd5 ffff9fba7f543ac0 ffff9fb9cb6ca5a0
May 24 12:05:12 vps2 kernel: [3729926.256488] ffffffffc06b4a58 0000000000000000 0000000004772296 0000000000000000
May 24 12:05:12 vps2 kernel: [3729926.256492] ffffab7701f7bd40 ffffffffc06ff997 ffff9fbb830dbac0 ffffffffc06fdcc4
May 24 12:05:12 vps2 kernel: [3729926.256495] Call Trace:
May 24 12:05:12 vps2 kernel: [3729926.256505] [<ffffffffb1329cd5>] ? dump_stack+0x5c/0x77
May 24 12:05:12 vps2 kernel: [3729926.256585] [<ffffffffc06b4a58>] ? xfs_attr3_leaf_write_verify+0xe8/0x100 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.256645] [<ffffffffc06ff997>] ? xfs_buf_delwri_submit_buffers+0x137/0x260 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.256712] [<ffffffffc06fdcc4>] ? _xfs_buf_ioapply+0x84/0x450 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.256719] [<ffffffffb10a2b30>] ? wake_up_q+0x60/0x60
May 24 12:05:12 vps2 kernel: [3729926.256781] [<ffffffffc06ff997>] ? xfs_buf_delwri_submit_buffers+0x137/0x260 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.256845] [<ffffffffc06ff6d7>] ? xfs_buf_submit+0x67/0x1f0 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.256911] [<ffffffffc06ff997>] ? xfs_buf_delwri_submit_buffers+0x137/0x260 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.256975] [<ffffffffc073177b>] ? xfsaild+0x2cb/0x7b0 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.257038] [<ffffffffc06ff365>] ? xfs_buf_unlock+0x15/0x70 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.257105] [<ffffffffc073177b>] ? xfsaild+0x2cb/0x7b0 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.257174] [<ffffffffc07314b0>] ? xfs_trans_ail_cursor_first+0x80/0x80 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.257182] [<ffffffffb10974c0>] ? kthread+0xe0/0x100
May 24 12:05:12 vps2 kernel: [3729926.257186] [<ffffffffb102476b>] ? __switch_to+0x2bb/0x700
May 24 12:05:12 vps2 kernel: [3729926.257189] [<ffffffffb10973e0>] ? kthread_park+0x60/0x60
May 24 12:05:12 vps2 kernel: [3729926.257194] [<ffffffffb15fb675>] ? ret_from_fork+0x25/0x30
May 24 12:05:12 vps2 kernel: [3729926.257201] XFS (dm-2): xfs_do_force_shutdown(0x8) called from line 1323 of file /home/zumbi/linux-4.9.13/fs/xfs/xfs_buf.c. Return address = 0xffffffffc06fe084
May 24 12:05:12 vps2 kernel: [3729926.260093] XFS (dm-2): Corruption of in-memory data detected. Shutting down filesystem
May 24 12:05:12 vps2 kernel: [3729926.262115] CPU: 1 PID: 454 Comm: xfsaild/dm-2 Tainted: G E 4.9.0-0.bpo.2-amd64 #1 Debian 4.9.13-1~bpo8+1
May 24 12:05:12 vps2 kernel: [3729926.262117] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/14/2014
May 24 12:05:12 vps2 kernel: [3729926.262120] 0000000000000000 ffffffffb1329cd5 0000000000000008 ffff9fbc275f3000
May 24 12:05:12 vps2 kernel: [3729926.262125] ffffffffc07061fa ffffffffc06fe084 0000000000000000 ffffab7701f7bd40
May 24 12:05:12 vps2 kernel: [3729926.262129] ffffffffc06ff997 ffff9fbb830dbac0 ffffffffc06fe084 ffff9fb934f86080
May 24 12:05:12 vps2 kernel: [3729926.262133] Call Trace:
May 24 12:05:12 vps2 kernel: [3729926.262141] [<ffffffffb1329cd5>] ? dump_stack+0x5c/0x77
May 24 12:05:12 vps2 kernel: [3729926.262228] [<ffffffffc07061fa>] ? xfs_do_force_shutdown+0x13a/0x140 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262294] [<ffffffffc06fe084>] ? _xfs_buf_ioapply+0x444/0x450 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262361] [<ffffffffc06ff997>] ? xfs_buf_delwri_submit_buffers+0x137/0x260 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262427] [<ffffffffc06fe084>] ? _xfs_buf_ioapply+0x444/0x450 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262433] [<ffffffffb10a2b30>] ? wake_up_q+0x60/0x60
May 24 12:05:12 vps2 kernel: [3729926.262503] [<ffffffffc06ff997>] ? xfs_buf_delwri_submit_buffers+0x137/0x260 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262573] [<ffffffffc06ff6d7>] ? xfs_buf_submit+0x67/0x1f0 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262643] [<ffffffffc06ff997>] ? xfs_buf_delwri_submit_buffers+0x137/0x260 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262717] [<ffffffffc073177b>] ? xfsaild+0x2cb/0x7b0 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262789] [<ffffffffc06ff365>] ? xfs_buf_unlock+0x15/0x70 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262864] [<ffffffffc073177b>] ? xfsaild+0x2cb/0x7b0 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262939] [<ffffffffc07314b0>] ? xfs_trans_ail_cursor_first+0x80/0x80 [xfs]
May 24 12:05:12 vps2 kernel: [3729926.262944] [<ffffffffb10974c0>] ? kthread+0xe0/0x100
May 24 12:05:12 vps2 kernel: [3729926.262948] [<ffffffffb102476b>] ? __switch_to+0x2bb/0x700
May 24 12:05:12 vps2 kernel: [3729926.262950] [<ffffffffb10973e0>] ? kthread_park+0x60/0x60
May 24 12:05:12 vps2 kernel: [3729926.262955] [<ffffffffb15fb675>] ? ret_from_fork+0x25/0x30
May 24 12:05:12 vps2 kernel: [3729926.263078] XFS (dm-2): Please umount the filesystem and rectify the problem(s)
After filesystem shutdown, before reboot i have upgraded kernel to 4.9.25-1~bpo8+1
Customer was calling us, just when nagios alerted us on host problem, that he was copying some files between accounts (which means changing acls), i have asked him for more information.
Libor
next prev parent reply other threads:[~2017-05-24 11:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 18:06 [PATCH] xfs_repair: junk leaf attribute if count == 0 Eric Sandeen
2016-12-12 18:36 ` Brian Foster
2016-12-13 10:52 ` Libor Klepáč
2016-12-13 16:04 ` Eric Sandeen
2016-12-15 20:48 ` Libor Klepáč
2016-12-21 8:25 ` Libor Klepáč
2016-12-24 17:50 ` Eric Sandeen
2017-01-31 8:03 ` Libor Klepáč
2017-03-13 13:48 ` Libor Klepáč
2017-03-13 14:14 ` Eric Sandeen
2017-03-14 8:15 ` Libor Klepáč
2017-03-14 16:54 ` Eric Sandeen
2017-03-14 18:51 ` Eric Sandeen
2017-03-15 10:07 ` Libor Klepáč
2017-03-15 15:22 ` Eric Sandeen
2017-03-16 8:58 ` Libor Klepáč
2017-03-16 15:21 ` Eric Sandeen
2017-03-29 13:33 ` Libor Klepáč
2017-04-11 11:23 ` Libor Klepáč
2017-05-24 11:18 ` Libor Klepáč [this message]
2017-05-24 12:24 ` Libor Klepáč
2017-02-01 12:48 ` Libor Klepáč
2017-02-01 22:49 ` Eric Sandeen
2017-02-02 8:35 ` Libor Klepáč
2017-02-22 11:42 ` Libor Klepáč
2017-02-22 13:45 ` Eric Sandeen
2017-02-22 14:19 ` Libor Klepáč
2017-02-23 9:05 ` 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=4648960.1DrcVCcZxK@libor-nb \
--to=libor.klepac@bcom.cz \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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).