Hi All,
We have been migrating from in-guest iscsi attached volumes to vmdk's. We have recently experienced a problem where one volume on a server that has five additional volumes, ran out space. This caused the other five volumes and their shares to become inaccessible, until the alert in vcenter stating the vmdk file that had run out of space, was increased and acknowledged.
I am trying to understand why one vmdk volume running out of space would have caused these additional volumes, that are each separate vmdk's by the way, to have become inaccessible until such time as that one volume that was out of space was expanded, and the alert was acknowledged. This is behavior unlike anything I have experienced with using in-guest iscsi connections - in which case it is expected that if one volume runs out of space it does NOT impact any other volumes on the same server.
I am hoping someone is able to provide some additional clarification around this behavior.
Thank you