[Bug 917134] Re: dbrd8 kernel module and padlock-sha kernel module in deadlock

[Adam Gandelman]

Hi Jens-

Thanks for reporting this.  This sounds like a tough one to debug, any
chance you've hit this again since reporting? I assume this is on a
production system and there's no chance of you trying to reproduce on
demand.  In the event that you do hit this again, before rebooting, can
you capture the output of 'dmesg', 'cat /proc/drbd', 'ps aux | grep "D
"' and 'netstat -ntp | grep 7788' (or whatever port the resource is
configured to use) from both nodes.  Also syslogs from both nodes would
be helpful as well as your drbd.conf (with any sensitive information
edited)

When you say your device got messed up, do you mean there was divergent
data on both nodes or that they disconnected and were required to carry
out a normal resync?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to drbd8 in Ubuntu.
https://bugs.launchpad.net/bugs/917134

Title:
  dbrd8 kernel module and padlock-sha kernel module in deadlock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/917134/+subscriptions