All of lore.kernel.org
 help / color / mirror / Atom feed
From: LinuxSysPro <linuxsyspro@gmail.com>
To: linux-scsi@vger.kernel.org
Subject: SCSI Reservation Conflicts errors.
Date: Wed, 15 Apr 2009 21:38:30 -0700 (PDT)	[thread overview]
Message-ID: <23071311.post@talk.nabble.com> (raw)


Hi All,

I'm getting many reservation conflicts error messages on initiator
size when logged-in to the iSCSI target device. Please help me in
resolving this problem.

In the target size we have Persistent Reservation implemented and I am
adding Mode Pages support in the target side. So is it due to the this
persistent reservation? Or what is the reason of getting those
conflicts? Correct me if I am wrong.

I read the SPC-3 & SBC, but I am not cleared(understood) regarding
this Reservation Conflicts.

Please help me.

Thanks in advance. 
-- 
View this message in context: http://www.nabble.com/SCSI-Reservation-Conflicts-errors.-tp23071311p23071311.html
Sent from the linux-scsi mailing list archive at Nabble.com.


             reply	other threads:[~2009-04-16  4:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16  4:38 LinuxSysPro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-04-24  7:37 SCSI Reservation Conflicts errors himanshu padmanabhi

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=23071311.post@talk.nabble.com \
    --to=linuxsyspro@gmail.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.