We recently purchased a Drobo Pro to be connected by iSCSI to our virtualisation solution (it’s a Debian/KVM setup running open-iscsi).
The Drobo resets itself periodically while the drives are being written to. This makes all the VMs panic (since all VMs stop seeing their disks). When the Drobo Finally decides to restart and comes back online, all filesystems are mounted read-only (as is default in most linux installs)
Obviously, this disqualifies the Drobo as anything remotely close to being useable. We are very disappointed by this. Sure, we didn’t expect blasing speeds (it’s only iSCSI), but we would at least assume that it would work overnight without having to reboot VMs in the morning because they failed during the nightly cron run (backups!).
Does anybody know of a magic “it makes the iSCSI work as advertized” solution? I tried tweaking iSCSI queue size and timeout behavior, no luck so far.
Also, opening a support case didn’t prove so helpful (waiting for an answer still).