Hi
@trasz@!
I´m struggilng making sense of using
ctld together with Windows 2012R2, presenting a lun to multiple initiators to create a Cluster Shared Volume (CSV). If using
istgt, it does present itself and you are able to create the CSV but it fails cluster validation on persistent reservations. If i stop
istgt and instead fire up
ctld serving the exact same volume (a ZVOL), you cannot create the CSV at all, it doesn´t show up as a resource to create the volume with. Tried setting up the CSV manually through
cmd.exe gave:
Code:
cluster res "res1" /create /group:"Available Storage" /type:"Physical Disk"
cluster res "res1" /priv diskpath="Q:"
cluster res "res1" /on
Error 1069: Cluster resource 'res1' of type 'Physical Disk' in clustered role 'Available Storage' failed. The error code was '0x2' ('The system cannot find the file specified.').
My goal would be to have FreeBSD with
ctld as a backing store for running Hyper-V virtualization in Windows 2012R2.
I have seen that work has been done (by you even) making
ctld stable together with Microsoft Failover Cluster and so this machine has been upped to 10-STABLE (r266795), but I just can´t seem to figure out how to get this working. No problems initiating the target from both hosts, partitioning, creating filesystem, copying and such, but no dice creating the CSV to use together with Hyper-V.
Any pointers on how to get the CSV part sorted?
/Sebulon