Hello T10/SCSI folks, A question came up on the LIO target-devel mailing list recently wrt the proper handling of Persistent Reservations + All Registrants logic in a couple of different scenarios. The crux of the confusion stems from how registrations are treated before an explicit PR-OUT RESERVE service action with All Registrants type occurs, and after that explicit PR-OUT RESERVE of All Registrants type has been released. My original interpretation was that an explicit PR-OUT RESERVE with All Registrants type had to first occur before other non reservation holding registrations (existing or not) would gain the implicit reservation. This was primarily because the reservation type was not known until the explicit PR-OUT RESERVE occurred, and AFAICT at the time there where no host implementations that actually specified the reservation type at registration time. So Is it correct to assume that one explicit PR-OUT RESERVE with All Registrants type needs to occur before other non reservation holding registrations gain an implicit reservation..? How about when the explicit reservation is removed..? Do the implicit reservations need to remain in effect for the existing registrations, even though the explicit reservation of All Registrants type no longer exists..? The second point that Ilias raised is what should be the correct R_HOLDER bit status for PRIN READ_FULL_STATUS descriptors when All Registrants type is specified. My original interpretation was that R_HOLDER was to signal the explicit reservation holder obtained with PR-OUT RESERVE, and not for the implicit reservations from the other registrations. Is this the correct approach..? Also, does anyone have any experience with a host side implementation of All Registrants to use as a reference for what's already out in the wild..? Thank you, --nab FYI, the pointer to Ilias's original question and my response with additional background is available here: http://comments.gmane.org/gmane.linux.scsi.target.devel/7632 -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
