Re: deadlocks in rbd unmap and map

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jul 8, 2016 at 3:28 AM, Patrick McLean <patrickm@xxxxxxxxxx> wrote:
> This is on linus git master as of 2016/07/01
>
> These appear to be two separate deadlocks, one on a a map operation,
> and one on an unmap operation. We can reproduce these pretty
> regularly, but it seems like there is some sort of race condition, as
> it happens no where near every time.
>
> We are currently working to reproduce on a kernel with lockdep
> enabled, as well as better debugging information. Please let me know
> if I can provide any more information.

I can see what happened from the traces, so no need to bother with
lockdep.  Figuring out how and why is trickier...

It's a single deadlock between "rbd map" and a kworker thread, a later
"rbd unmap" is just a victim.

Are you mapping the same image more than once?

Thanks,

                Ilya
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux