From: Douglas Gilbert <dougg@torque.net>
To: "Jansen, Frank" <fjansen@egenera.com>
Cc: djshetty <dhirajshetty.junk@mailnull.com>, linux-scsi@vger.kernel.org
Subject: Re: Persistent Reservation
Date: Thu, 16 Nov 2006 12:52:46 -0500 [thread overview]
Message-ID: <455CA56E.202@torque.net> (raw)
In-Reply-To: <216D6FA68B0F304DA93E95C5B786F2D17C8439@bart.corp.egenera.com>
Jansen, Frank wrote:
> Dhiraj,
>
> In the most common case, persistent reservations are stored with the
> device, such as the storage array. Note that not all devices
> implement/support persistent reservations and there are cases where the
> reservations are stored elsewhere, which tends to be the approach in
> virtualizing environments.
The linux SCSI subsystem doesn't interact with lu
persistent reservations. Last time I looked, the
kernel was pretty noisy when a RESERVATION CONFLICT
status was received, even via a sg device node.
You can manipulate persistent reservations from the
user space with sg_persist in sg3_utils package.
Device support for persistent reservations is improving,
Fujitsu SCSI disks have had it for some time. I
noticed that the Seagate 15K.5 series support those
commands while the 15K.4 series and earlier didn't.
Doug Gilbert
>> -----Original Message-----
>> From: linux-scsi-owner@vger.kernel.org
>> [mailto:linux-scsi-owner@vger.kernel.org] On Behalf Of djshetty
>> Sent: Thursday, November 16, 2006 7:27 AM
>> To: linux-scsi@vger.kernel.org
>> Subject: Persistent Reservation
>>
>>
>> Hi,
>>
>> I had a doubt. In order to persist the reservation we need to
>> store some information like reservation keys, scope, type of
>> reservation etc.
>>
>> Where exactly are such information stored and by whom ?
>>
>> Regards,
>> Dhiraj
>> --
>> View this message in context:
>> http://www.nabble.com/Persistent-Reservation-tf2642680.html#a7376789
>> Sent from the linux-scsi mailing list archive at Nabble.com.
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-scsi" in the body of a message to
>> majordomo@vger.kernel.org More majordomo info at
>> http://vger.kernel.org/majordomo-info.html
>>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-11-16 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 13:46 Persistent Reservation Jansen, Frank
2006-11-16 17:52 ` Douglas Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-16 12:27 djshetty
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=455CA56E.202@torque.net \
--to=dougg@torque.net \
--cc=dhirajshetty.junk@mailnull.com \
--cc=fjansen@egenera.com \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.