Sorry for the noise, but I've probably run into a regression where when I attempt to validate a Microsoft failover cluster with an iSCSI target host running kernel 3.8.3. Microsoft's failover cluster validation tests returns the following error when it attempts to pass the "SCSI-3 Persistent Reservation" test: Success returned calling Persistent Reservation PREEMPT by node HVCLUSTER2.smb.curriegrad2004.ca which was not registered on Test Disk 0 which was currently reserved by node HVCLUSTER1.smb.curriegrad2004.ca. It is expected to fail. When I perform a dmesg I see the following kernel messages: [ 379.846756] SPC-3 PR: Attempted RESERVE from [iSCSI]: iqn.1991-05.com.microsoft:hvcluster1.smb.curriegrad2004.ca while reservation already held by [iSCSI]: iqn.1991-05.com.microsoft:hvcluster2.smb.curriegrad2004.ca, returning RESERVATION_CONFLICT [ 379.878579] SPC-3 PR: Attempted RESERVE from [iSCSI]: iqn.1991-05.com.microsoft:hvcluster1.smb.curriegrad2004.ca while reservation already held by [iSCSI]: iqn.1991-05.com.microsoft:hvcluster2.smb.curriegrad2004.ca, returning RESERVATION_CONFLICT [ 380.921863] SPC-3 PR: Unable to locate PR_REGISTERED *pr_reg for RELEASE [ 380.928377] SPC-3 PR: Unable to locate PR_REGISTERED *pr_reg for RELEASE [ 380.974719] SPC-3 PR: Unable to locate PR_REGISTERED *pr_reg for RELEASE [ 380.985632] SPC-3 PR: Unable to locate PR_REGISTERED *pr_reg for RELEASE [ 381.481037] SPC-3 PR: Unable to locate PR_REGISTERED *pr_reg for RELEASE [ 381.989328] SPC-3 PR: Unable to locate PR_REGISTERED *pr_reg for RELEASE To verify that it may be a regression, I've compiled the 3.2 kernel from Ubuntu's git and re-validated the cluster. That kernel validated just fine. Is anybody here experiencing this problem or did I do something wrong? -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
