From: Lee Duncan <lduncan@suse.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "t10@t10.org" <t10@t10.org>,
target-devel <target-devel@vger.kernel.org>,
Ilias Tsitsimpis <i.tsitsimpis@gmail.com>,
"Elliott, Robert (Server Storage)" <Elliott@hp.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Clarification for Persistent Reservation + All Registrants
Date: Wed, 17 Dec 2014 15:46:45 -0800 [thread overview]
Message-ID: <549215E5.905@suse.com> (raw)
In-Reply-To: <1418538447.5431.56.camel@haakon3.risingtidesystems.com>
Sorry to come to this late, but I have one addition ...
On 12/13/2014 10:27 PM, Nicholas A. Bellinger wrote:
> On Sat, 2014-12-13 at 08:33 +0100, James Bottomley wrote:
>> On Fri, 2014-12-12 at 17:53 -0800, Nicholas A. Bellinger wrote:
>>> On Sat, 2014-12-13 at 00:52 +0100, James Bottomley wrote:
>>>> On Fri, 2014-12-12 at 14:59 -0800, Nicholas A. Bellinger wrote:
> lots of SNIP
>>
>> There is no reservation until a reserve command is issued. Once an all
>> registrants reservation is issued, by any registered initator, all
>> registered initators then become the reservation holder.
>>
>
> So based on the above, the issue raised by Ilias where once the original
> All Registrants reservation is released, the other registrations lose
> their 'implicit' reservation until someone does another RESERVE +
> type=All Registrants is a bug.
U belive your target Nicholas is working correctly. See that other
thread for more details.
>
> Working on a proper bugfix for this now.
>
> Thanks James!
>
> --nab
>
--
Lee Duncan
prev parent reply other threads:[~2014-12-17 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 22:59 Clarification for Persistent Reservation + All Registrants Nicholas A. Bellinger
2014-12-12 23:52 ` James Bottomley
2014-12-13 1:53 ` Nicholas A. Bellinger
2014-12-13 7:33 ` James Bottomley
2014-12-14 6:27 ` Nicholas A. Bellinger
2014-12-17 23:46 ` Lee Duncan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=549215E5.905@suse.com \
--to=lduncan@suse.com \
--cc=Elliott@hp.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=i.tsitsimpis@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=t10@t10.org \
--cc=target-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox