From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: 4.1-rc2 dm-multipath-mq kernel warning
Date: Wed, 27 May 2015 17:33:55 +0200 [thread overview]
Message-ID: <5565E3E3.4080801@sandisk.com> (raw)
In-Reply-To: <5565E2EA.2000302@sandisk.com>
On 05/27/15 17:29, Bart Van Assche wrote:
> On 05/27/15 14:57, Mike Snitzer wrote:
>> Looks like Junichi likely fixed this issue you reported, please try this
>> patch: https://patchwork.kernel.org/patch/6487321/
>
> Hello Mike,
>
> On a setup on which an I/O verification test passes with
> blk-mq/scsi-mq/dm-mq disabled, this is what fio reports after a few
> minutes with scsi-mq and dm-mq enabled:
>
> test: Laying out IO file(s) (1 file(s) / 10MB)
> fio: io_u error on file /mnt/test.0.0: Input/output error: write
> offset=8327168, buflen=4096
> fio: io_u error on file /mnt/test.0.0: Input/output error: write
> offset=9007104, buflen=4096
> fio: pid=4568, err=5/file:io_u.c:1564, func=io_u error,
> error=Input/output error
(replying to my own e-mail)
BTW, on the same test setup kmemleak reports several memory leaks, e.g.
this one:
unreferenced object 0xffff88009b14e2b0 (size 16):
comm "fio", pid 4274, jiffies 4294978034 (age 1253.210s)
hex dump (first 16 bytes):
40 12 f3 99 01 88 ff ff 00 10 00 00 00 00 00 00 @...............
backtrace:
[<ffffffff81600029>] kmemleak_alloc+0x49/0xb0
[<ffffffff811679a8>] kmem_cache_alloc+0xf8/0x160
[<ffffffff8111c950>] mempool_alloc_slab+0x10/0x20
[<ffffffff8111cb37>] mempool_alloc+0x57/0x150
[<ffffffffa04d2b61>] __multipath_map.isra.17+0xe1/0x220 [dm_multipath]
[<ffffffffa04d2cb5>] multipath_clone_and_map+0x15/0x20 [dm_multipath]
[<ffffffffa02889b5>] map_request.isra.39+0xd5/0x220 [dm_mod]
[<ffffffffa028b0e4>] dm_mq_queue_rq+0x134/0x240 [dm_mod]
[<ffffffff812cccb5>] __blk_mq_run_hw_queue+0x1d5/0x380
[<ffffffff812ccaa5>] blk_mq_run_hw_queue+0xc5/0x100
[<ffffffff812ce350>] blk_sq_make_request+0x240/0x300
[<ffffffff812c0f30>] generic_make_request+0xc0/0x110
[<ffffffff812c0ff2>] submit_bio+0x72/0x150
[<ffffffff811c07cb>] do_blockdev_direct_IO+0x1f3b/0x2da0
[<ffffffff811c166e>] __blockdev_direct_IO+0x3e/0x40
[<ffffffff8120aa1a>] ext4_direct_IO+0x1aa/0x390
Bart.
next prev parent reply other threads:[~2015-05-27 15:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 14:04 4.1-rc2 dm-multipath-mq kernel warning Bart Van Assche
2015-05-06 2:23 ` Mike Snitzer
2015-05-06 7:45 ` Bart Van Assche
2015-05-06 18:29 ` Mike Snitzer
2015-05-07 10:19 ` Bart Van Assche
2015-05-27 12:57 ` Mike Snitzer
2015-05-27 15:29 ` Bart Van Assche
2015-05-27 15:33 ` Bart Van Assche [this message]
2015-05-27 16:14 ` Mike Snitzer
2015-05-27 17:00 ` Mike Snitzer
2015-05-27 22:37 ` Mike Snitzer
2015-05-28 8:19 ` Bart Van Assche
2015-05-28 13:10 ` Mike Snitzer
2015-05-28 14:07 ` Mike Snitzer
2015-05-28 14:54 ` Bart Van Assche
2015-05-28 15:06 ` Mike Snitzer
2015-05-29 10:04 ` Bart Van Assche
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=5565E3E3.4080801@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=dm-devel@redhat.com \
--cc=snitzer@redhat.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.