Bug: creating clustered storage doesn't check existing names

[robnicholson]

See attached screenshots. In sshot-36, you can see there is already storage called "Storage1". In sshot-37, I'm going through creating additional storage. This is where the bug starts to appear - it should have queried the cluster/nodes to work out the next free storage name - Storage2 in this case. StarWind does this when creating the storage manually on the nodes. The wizard should do the same.

So if you don't spot the duplicate storage name, and carry on (see sshot-38 for settings), you get "Storage creation failed" as in sshot-39 which isn't surprising.

But it gets a bit worse - you end up with the configuration as shown in sshot-40 and a novice could be pretty worried here. Especially if you then manually removed those targets (storage1_1) and wondered if StarWind had already created the associated files on disk. So you look at the disk as in sshot-41 and go "ah yes, it has created a file called storage1_1" and delete it.

EXCEPT you've just deleted a key file from the existing storage - storage1_1.spspx is actually the first disk on the existing LSFS. Bang - you've just broken the existing storage.

Little too many options here for easily making a right old mess IMO - esp. if this was a production server and you've just deleted part of an existing LSFS device...

Cheers, Rob.

[Anatoly (staff)]

Good catch!

I`ll pass it along to fix right now.

Thanks!

P.S. I still owe you a beer

[Anatoly (staff)]

UPDATE: we`ll get the fix in the next minor update.