Messages in this thread |  | | | Date | Thu, 17 Mar 2011 19:31:03 +0100 | | From | Jens Axboe <> | | Subject | Re: [PATCH 05/10] block: remove per-queue plugging |
| |
On 2011-03-17 16:51, Mike Snitzer wrote: > On Tue, Mar 08 2011 at 5:05pm -0500, > Mike Snitzer <snitzer@redhat.com> wrote: > >> On Tue, Mar 08 2011 at 3:27pm -0500, >> Jens Axboe <jaxboe@fusionio.com> wrote: >> >>> On 2011-03-08 21:21, Mike Snitzer wrote: >>>> On Tue, Mar 08 2011 at 7:16am -0500, >>>> Jens Axboe <jaxboe@fusionio.com> wrote: >>>> >>>>> On 2011-03-03 23:13, Mike Snitzer wrote: >>>>>> I'm now hitting a lockdep issue, while running a 'for-2.6.39/stack-plug' >>>>>> kernel, when I try an fsync heavy workload to a request-based mpath >>>>>> device (the kernel ultimately goes down in flames, I've yet to look at >>>>>> the crashdump I took) >>>>> >>>>> Mike, can you re-run with the current stack-plug branch? I've fixed the >>>>> !CONFIG_BLOCK and rebase issues, and also added a change for this flush >>>>> on schedule event. It's run outside of the runqueue lock now, so >>>>> hopefully that should solve this one. >>>> >>>> Works for me, thanks. >>> >>> Super, thanks! Out of curiousity, did you use dm/md? >> >> Yes, I've been using a request-based DM multipath device. > > > Against latest 'for-2.6.39/core', I just ran that same fsync heavy > workload against XFS (ontop of a DM multipath volume). ffsb induced the > following hangs (ripple effect causing NetworkManager to get hung up on > this data-only XFS volume, etc):
Ugh. Care to send the recipee for how to reproduce this? Essentially just looks like IO got stuck.
-- Jens Axboe
|  |