Hi, <br><br>We found the problem, and the solution as well.<br>The problem was that there was inconsistency in the gluster storage volume which was underneath the libvirt storage pool. One file in multiple locations with different sizes. After this fixing those inconsistencies pool-start worked correctly. <br>
<br>But the error message from virsh was way off.<br><br>Best regards<br>Raggi Skula<br>
<br><br><div class="gmail_quote">On Tue, Sep 4, 2012 at 9:45 AM, Ragnar Skúlason <span dir="ltr">&lt;<a href="mailto:raggi@greenqloud.com" target="_blank">raggi@greenqloud.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi everyone,<br><br>I&#39;m not sure if this belongs here, I sent a question to the users list yesterday without getting a response, so I&#39;m trying here.<br><br>I have storage-pool that for some reason became 
inactive (possibly due to an error with pool-refresh in an old version 
of a Java API binding).<br><br>I want to restart the pool but am unable to, due to the volume being mounted: <br>
<br># virsh pool-start [uuid]<br>error: Failed to start pool [uuid]<br>error: Requested operation is not valid: Target &#39;/mnt/[uuid]&#39; is already mounted<br><br>We have tested this with versions 0.9.12 and 0.9.13.<br>

<br>This did work in versions 0.8.x<br>
<br>Is it possible to bypass this mount check and start the storage pool (forcefully)?<br><br>Many thanks,<br>Ragnar Skúlason
</blockquote></div><br>