From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "xfs-masters@oss.sgi.com" <xfs-masters@oss.sgi.com>
Cc: holger@applied-asynchrony.com, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: _xfs_buf_ioapply: no ops on block 0x188e78/0x8 on vanilla 4.4.11
Date: Thu, 2 Jun 2016 15:23:31 +0200 [thread overview]
Message-ID: <57503353.2050402@profihost.ag> (raw)
Hi,
another issue i'm having with 4.4.11 is the following trace after a reboot:
[ 541.661121] XFS (dm-0): _xfs_buf_ioapply: no ops on block 0x188e78/0x8
[ 541.662423] ffff88013a3b3000: 44 51 01 01 00 00 00 00 00 00 00 00 00
00 00 00 DQ..............
[ 541.663258] ffff88013a3b3010: 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 ................
[ 541.664156] ffff88013a3b3020: 00 00 00 00 00 00 00 00 00 00 00 00 00
0b db fd ................
[ 541.664930] ffff88013a3b3030: 00 00 00 00 00 01 9e 82 00 00 00 00 00
00 00 00 ................
[ 541.665704] CPU: 0 PID: 489 Comm: xfsaild/dm-0 Not tainted 4.4.11 #1
[ 541.666486] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
[ 541.667276] 0000000000000000 ffff880037a57c70 ffffffffbe3b3c33
0000000000000001
[ 541.668094] ffff880139d16900 ffff880037a57d18 ffffffffbe31c681
0000000000000000
[ 541.668896] ffff880139d16980 0000000000000000 0000000000000000
0000000000000000
[ 541.669705] Call Trace:
[ 541.670491] [<ffffffffbe3b3c33>] dump_stack+0x63/0x90
[ 541.671286] [<ffffffffbe31c681>] _xfs_buf_ioapply+0x3e1/0x440
[ 541.672113] [<ffffffffbe0aaba0>] ? wake_up_q+0x70/0x70
[ 541.672901] [<ffffffffbe31df99>] ? __xfs_buf_delwri_submit+0x179/0x270
[ 541.673704] [<ffffffffbe31dcc4>] xfs_buf_submit+0x64/0x1c0
[ 541.674506] [<ffffffffbe31df99>] __xfs_buf_delwri_submit+0x179/0x270
[ 541.675321] [<ffffffffbe31eea0>] ?
xfs_buf_delwri_submit_nowait+0x20/0x30
[ 541.676129] [<ffffffffbe31eea0>] xfs_buf_delwri_submit_nowait+0x20/0x30
[ 541.676930] [<ffffffffbe3495f6>] xfsaild+0x2a6/0x710
[ 541.677738] [<ffffffffbe349350>] ? xfs_trans_ail_cursor_first+0x90/0x90
[ 541.678557] [<ffffffffbe349350>] ? xfs_trans_ail_cursor_first+0x90/0x90
[ 541.679357] [<ffffffffbe09f36b>] kthread+0xdb/0x100
[ 541.680136] [<ffffffffbe09f290>] ? kthread_park+0x60/0x60
[ 541.680912] [<ffffffffbe6972cf>] ret_from_fork+0x3f/0x70
[ 541.681708] [<ffffffffbe09f290>] ? kthread_park+0x60/0x60
I found a bug report from redhat here
https://bugzilla.redhat.com/show_bug.cgi?id=1234586 pointing to this commit:
xfs: handle dquot buffer readahead in log recovery correctly
which isn't part of 4.4. Is it missing from linux-stable?
i'm using XFS V5 with root quotas on in this case.
Greets,
Stefan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-06-02 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 13:23 Stefan Priebe - Profihost AG [this message]
2016-06-02 14:05 ` _xfs_buf_ioapply: no ops on block 0x188e78/0x8 on vanilla 4.4.11 Holger Hoffstätte
2016-06-02 14:21 ` Holger Hoffstätte
2016-06-02 22:25 ` Dave Chinner
2016-06-02 22:43 ` Holger Hoffstätte
2016-06-03 17:43 ` Stefan Priebe - Profihost AG
2016-06-03 19:29 ` Holger Hoffstätte
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=57503353.2050402@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=holger@applied-asynchrony.com \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.com \
/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.