<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><br>Hello, <br><br>I am not running nfs, but I am seeing the problem.<br>"State change failed: (-12) Device is held open by someone"<br> In my case the problem is intermittent. Most failovers are
<br>successful, but every so often the "device is held open" error occurs.
<br><br>Then the heartbeat will reboot the active machine when this
<br>problem occurs and proceed with the failover to the standby. Everything
<br>works fine after the reboot; the machine comes back up in secondary
<br>state as expected. However, I'd like to fix the problem and thus prevent
<br>the reboot from occurring. <br><br>I am able to reproduce the problem in an
environment where the machine <br>does not reboot (it stays in the "device is
held open" state). At this <br>point I execute commands "lsof", "fuser -mv",
"ps", and look at <br>/proc/mounts, but I cannot figure out who is holding open
the drbd <br>device. I am running LVM on top of DRBD. It looks to me like my
<br>application has been shut down cleanly, files have been unmounted, and
<br>the LVM volume group has been deactivated. <br><br>I looked at the DRBD
source code in an attempt to understand how it <br>determines that the device is
held open. It looks like it is based on an <br>internal count of open devices.
<br><br>Any tips or suggestions would be greatly appreciated on how to further
<br>debug the problem. <br><br>I am running DRBD version 8.0.11 and heartbeat
version 2.1.3. <br><br><strong><font color="#ff80bf"><br></font></strong></td></tr></table><br>