GladeCreek
Cadet
- Joined
- Jan 7, 2013
- Messages
- 2
I have seen several nicely written guides on how to setup Cluster Shared Volumes on FreeNAS, and I have read forum posts of people doing it successfully, but then I've seen quite a few posts from folks that can not get it to work. I'm in the 'not working' category.
I'm running FreeNAS 8.3.0p1, and I've tried both device extents and file extents with similar results. The attached servers are running Hyper-V 2012 RTM, and can see the presented volumes (initialize, format, etc.), but I run in to a snag when attempting to use them as CSV volumes. Below is the output from the Validation. I thought perhaps the verbose message might jog something in someone's mind.
Is this really a problem with the underlying iSCSI package that FreeNAS uses? Or could it be something as simple as the Target authentication settings.
If anyone has this working with any version of Microsoft OS CSV, please post your settings so that I might try to emulate in my lab. Thanks very much.
Validate SCSI-3 Persistent Reservation
Description: Validate that storage supports the SCSI-3 Persistent Reservation commands.
Start: 1/7/2013 12:37:17 PM.
Validating Test Disk 1 for Persistent Reservation support.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING for Test Disk 1 from node HYPERV04.GCT.local.
Issuing call to Persistent Reservation RESERVE on Test Disk 1 from node HYPERV04.GCT.local.
Issuing Persistent Reservation READ RESERVATION on Test Disk 1 from node HYPERV04.GCT.local.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING for Test Disk 1 from node HYPERV03.GCT.local.
Issuing call to Persistent Reservation RESERVE on Test Disk 1 from node HYPERV03.GCT.local.
Issuing call Persistent Reservation PREEMPT on Test Disk 1 from unregistered node HYPERV03.GCT.local. This is expected to fail.
Issuing call to Persistent Reservation RESERVE on Test Disk 1 from node HYPERV03.GCT.local.
Failure issuing call to Persistent Reservation RESERVE on Test Disk 1 from node HYPERV03.GCT.local when that node has successfully registered. It is expected to succeed. The requested resource is in use.
.
Test Disk 1 does not provide Persistent Reservations support for the mechanisms used by failover clusters. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.
Validating Test Disk 0 for Persistent Reservation support.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING for Test Disk 0 from node HYPERV04.GCT.local.
Issuing call to Persistent Reservation RESERVE on Test Disk 0 from node HYPERV04.GCT.local.
Issuing Persistent Reservation READ RESERVATION on Test Disk 0 from node HYPERV04.GCT.local.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING for Test Disk 0 from node HYPERV03.GCT.local.
Issuing call to Persistent Reservation RESERVE on Test Disk 0 from node HYPERV03.GCT.local.
Issuing call Persistent Reservation PREEMPT on Test Disk 0 from unregistered node HYPERV03.GCT.local. This is expected to fail.
Issuing call to Persistent Reservation RESERVE on Test Disk 0 from node HYPERV03.GCT.local.
Failure issuing call to Persistent Reservation RESERVE on Test Disk 0 from node HYPERV03.GCT.local when that node has successfully registered. It is expected to succeed. The requested resource is in use.
.
Test Disk 0 does not provide Persistent Reservations support for the mechanisms used by failover clusters. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.Failure issuing call to Persistent Reservation RESERVE on Test Disk 0 from node HYPERV04.GCT.local when that node has successfully registered. It is expected to succeed. The requested resource is in use.
.
Failure issuing call to Persistent Reservation RESERVE on Test Disk 1 from node HYPERV04.GCT.local when that node has successfully registered. It is expected to succeed. The requested resource is in use.
.
Stop: 1/7/2013 12:37:18 PM.
Test failed. Please look at the test log for more information.
I'm running FreeNAS 8.3.0p1, and I've tried both device extents and file extents with similar results. The attached servers are running Hyper-V 2012 RTM, and can see the presented volumes (initialize, format, etc.), but I run in to a snag when attempting to use them as CSV volumes. Below is the output from the Validation. I thought perhaps the verbose message might jog something in someone's mind.
Is this really a problem with the underlying iSCSI package that FreeNAS uses? Or could it be something as simple as the Target authentication settings.
If anyone has this working with any version of Microsoft OS CSV, please post your settings so that I might try to emulate in my lab. Thanks very much.
Validate SCSI-3 Persistent Reservation
Description: Validate that storage supports the SCSI-3 Persistent Reservation commands.
Start: 1/7/2013 12:37:17 PM.
Validating Test Disk 1 for Persistent Reservation support.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING for Test Disk 1 from node HYPERV04.GCT.local.
Issuing call to Persistent Reservation RESERVE on Test Disk 1 from node HYPERV04.GCT.local.
Issuing Persistent Reservation READ RESERVATION on Test Disk 1 from node HYPERV04.GCT.local.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING for Test Disk 1 from node HYPERV03.GCT.local.
Issuing call to Persistent Reservation RESERVE on Test Disk 1 from node HYPERV03.GCT.local.
Issuing call Persistent Reservation PREEMPT on Test Disk 1 from unregistered node HYPERV03.GCT.local. This is expected to fail.
Issuing call to Persistent Reservation RESERVE on Test Disk 1 from node HYPERV03.GCT.local.
Failure issuing call to Persistent Reservation RESERVE on Test Disk 1 from node HYPERV03.GCT.local when that node has successfully registered. It is expected to succeed. The requested resource is in use.
.
Test Disk 1 does not provide Persistent Reservations support for the mechanisms used by failover clusters. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.
Validating Test Disk 0 for Persistent Reservation support.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING for Test Disk 0 from node HYPERV04.GCT.local.
Issuing call to Persistent Reservation RESERVE on Test Disk 0 from node HYPERV04.GCT.local.
Issuing Persistent Reservation READ RESERVATION on Test Disk 0 from node HYPERV04.GCT.local.
Issuing Persistent Reservation REGISTER AND IGNORE EXISTING for Test Disk 0 from node HYPERV03.GCT.local.
Issuing call to Persistent Reservation RESERVE on Test Disk 0 from node HYPERV03.GCT.local.
Issuing call Persistent Reservation PREEMPT on Test Disk 0 from unregistered node HYPERV03.GCT.local. This is expected to fail.
Issuing call to Persistent Reservation RESERVE on Test Disk 0 from node HYPERV03.GCT.local.
Failure issuing call to Persistent Reservation RESERVE on Test Disk 0 from node HYPERV03.GCT.local when that node has successfully registered. It is expected to succeed. The requested resource is in use.
.
Test Disk 0 does not provide Persistent Reservations support for the mechanisms used by failover clusters. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters.Failure issuing call to Persistent Reservation RESERVE on Test Disk 0 from node HYPERV04.GCT.local when that node has successfully registered. It is expected to succeed. The requested resource is in use.
.
Failure issuing call to Persistent Reservation RESERVE on Test Disk 1 from node HYPERV04.GCT.local when that node has successfully registered. It is expected to succeed. The requested resource is in use.
.
Stop: 1/7/2013 12:37:18 PM.
Test failed. Please look at the test log for more information.