From ips-bounces@ietf.org  Thu Jun  5 14:24:31 2008
Return-Path: <ips-bounces@ietf.org>
X-Original-To: ips-archive@optimus.ietf.org
Delivered-To: ietfarch-ips-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F30228C132;
	Thu,  5 Jun 2008 14:24:31 -0700 (PDT)
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 74B1428C0E4
	for <ips@core3.amsl.com>; Thu,  5 Jun 2008 14:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id qgBdhj8KSxeO for <ips@core3.amsl.com>;
	Thu,  5 Jun 2008 14:24:28 -0700 (PDT)
Received: from fmailhost03.isp.att.net (fmailhost03.isp.att.net
	[204.127.217.103])
	by core3.amsl.com (Postfix) with ESMTP id 92FDD3A6D8F
	for <ips@ietf.org>; Thu,  5 Jun 2008 14:23:43 -0700 (PDT)
Received: from ivvtdkv0981 (adsl-218-205-129.jax.bellsouth.net[68.218.205.129])
	by isp.att.net (frfwmhc03) with SMTP
	id <20080605212349H0300s4taee>; Thu, 5 Jun 2008 21:23:50 +0000
X-Originating-IP: [68.218.205.129]
Message-ID: <001901c8c752$73a57c90$0602a8c0@ivivity.com>
From: "Eddy Quicksall" <Quicksall_iSCSI@Bellsouth.net>
To: <ips@ietf.org>
References: <27885.65355.qm@web51704.mail.re2.yahoo.com>
Date: Thu, 5 Jun 2008 17:23:50 -0400
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: [Ips] OSD over iSCSI
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1438525841=="
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1438525841==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0016_01C8C730.EB71F1D0"

This is a multi-part message in MIME format.

------=_NextPart_000_0016_01C8C730.EB71F1D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I would like to test my target's support of long CDB's. So I'm looking =
for an iSCSI initiator that will carry long CDB's and hopefully an OSD =
version 2 file system (since OSD issues 200 byte CDB's). Does anyone =
know of anything or work in progress?

Eddy
------=_NextPart_000_0016_01C8C730.EB71F1D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<STYLE type=3Dtext/css>DIV {
	MARGIN: 0px
}
</STYLE>

<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>I would like to test my target's support of long=20
CDB's.&nbsp;So I'm looking for an iSCSI initiator that will carry long=20
CDB's&nbsp;and hopefully an OSD version 2 file system (since OSD issues =
200 byte=20
CDB's). Does anyone know of anything or work in progress?</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Eddy</FONT></DIV></BODY></HTML>

------=_NextPart_000_0016_01C8C730.EB71F1D0--


--===============1438525841==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips

--===============1438525841==--



From ips-bounces@ietf.org  Thu Jun  5 14:38:17 2008
Return-Path: <ips-bounces@ietf.org>
X-Original-To: ips-archive@optimus.ietf.org
Delivered-To: ietfarch-ips-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4854B3A69CD;
	Thu,  5 Jun 2008 14:38:17 -0700 (PDT)
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A2A83A6AF7
	for <ips@core3.amsl.com>; Thu,  5 Jun 2008 14:38:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.227
X-Spam-Level: *
X-Spam-Status: No, score=1.227 tagged_above=-999 required=5 tests=[AWL=-1.225, 
	BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4rYjAG9oKtxZ for <ips@core3.amsl.com>;
	Thu,  5 Jun 2008 14:38:15 -0700 (PDT)
Received: from fmailhost06.isp.att.net (fmailhost06.isp.att.net
	[204.127.217.106])
	by core3.amsl.com (Postfix) with ESMTP id 40CFD3A6ABB
	for <ips@ietf.org>; Thu,  5 Jun 2008 14:38:15 -0700 (PDT)
Received: from ivvtdkv0981 (adsl-218-205-129.jax.bellsouth.net[68.218.205.129])
	by isp.att.net (frfwmhc06) with SMTP
	id <20080605213822H060011v9se>; Thu, 5 Jun 2008 21:38:22 +0000
X-Originating-IP: [68.218.205.129]
Message-ID: <002d01c8c754$7b43cb80$0602a8c0@ivivity.com>
From: "Eddy Quicksall" <Quicksall_iSCSI@Bellsouth.net>
To: "HUJason" <hzj_wuying@hotmail.com>,
	<ips@ietf.org>
References: <4804B03C.6060507@voltaire.com><OFA528E763.71479425-ON8525742C.005B02F4-8825742C.005F18F1@us.ibm.com>
	<BAY135-W8D5029F9222302060E3B2F3EA0@phx.gbl>
	<BAY135-W474F400D055F9449FED2C5F3D60@phx.gbl>
Date: Thu, 5 Jun 2008 17:38:22 -0400
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [Ips] Write residual scenario
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0031906969=="
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0031906969==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002A_01C8C732.F388CC20"

This is a multi-part message in MIME format.

------=_NextPart_000_002A_01C8C732.F388CC20
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

For a disk underrun, you could issue a write(10) of one block but an =
Expected Data Transfer Length of 1. I don't know if that is an error for =
SCSI but it was not for earlier disk drives. In fact in the late '60s we =
did do that to initialize the sectors on a disk with the sector address =
... the rest of the sector would just get 0's. For an overrun, try =
writing 0 blocks but specify a positive Expected Data Transfer Length.

It may be more logical for some other types of devices.

Eddy
  ----- Original Message -----=20
  From: HUJason=20
  To: ips@ietf.org=20
  Sent: Monday, May 05, 2008 10:27 PM
  Subject: [Ips] Write residual scenario


  Dears,
  =20
  In RFC5048 There is a line describing the residual cases:
  =20
  > Note that the Overflow and Underflow scenarios are independent of
  > Data-In and Data-Out.  Either scenario is logically possible in
  > either direction of data transfer.
  =20
  Can anyone please picture a case for the Data-Out residual? I know it =
is logically possible, but when it happen it should be a "not good" =
write response, right?
  =20
  Thank you and Best Regards,

  Jason HU


-------------------------------------------------------------------------=
-----
  =D3=C3 Windows Live Spaces =
=D5=B9=CA=BE=B8=F6=D0=D4=D7=D4=CE=D2=A3=AC=D3=EB=BA=C3=D3=D1=B7=D6=CF=ED=C9=
=FA=BB=EE=A3=A1 =C1=CB=BD=E2=B8=FC=B6=E0=D0=C5=CF=A2=A3=A1=20


-------------------------------------------------------------------------=
-----


  _______________________________________________
  Ips mailing list
  Ips@ietf.org
  https://www.ietf.org/mailman/listinfo/ips

------=_NextPart_000_002A_01C8C732.F388CC20
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312">
<STYLE>.hmmessage P {
	PADDING-RIGHT: 0px; PADDING-LEFT: 0px; PADDING-BOTTOM: 0px; MARGIN: =
0px; PADDING-TOP: 0px
}
BODY.hmmessage {
	FONT-SIZE: 9pt; FONT-FAMILY: Tahoma
}
</STYLE>

<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR></HEAD>
<BODY class=3Dhmmessage bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>For a disk underrun, you could issue a =
write(10) of=20
one block but an Expected Data Transfer Length of 1. I don't know if =
that is an=20
error for SCSI but it was not for earlier disk drives. In fact in =
the&nbsp;late=20
'60s&nbsp;we did do that to initialize the sectors on a disk with the =
sector=20
address ... the rest of the sector would just get 0's. For an overrun, =
try=20
writing 0 blocks but specify a positive Expected Data Transfer=20
Length.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>It may be more logical for some other =
types of=20
devices.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Eddy</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dhzj_wuying@hotmail.com=20
  href=3D"mailto:hzj_wuying@hotmail.com">HUJason</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3Dips@ietf.org=20
  href=3D"mailto:ips@ietf.org">ips@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, May 05, 2008 =
10:27 PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Ips] Write residual=20
  scenario</DIV>
  <DIV><BR></DIV>Dears,<BR>&nbsp;<BR>In RFC5048 There is a line =
describing the=20
  residual cases:<BR>&nbsp;<BR>&gt; Note that the Overflow and Underflow =

  scenarios are independent of<BR>&gt; Data-In and Data-Out.&nbsp; =
Either=20
  scenario is logically possible in<BR>&gt; either direction of data=20
  transfer.<BR>&nbsp;<BR>Can&nbsp;anyone&nbsp;please picture a case for =
the=20
  Data-Out residual? I know it is logically possible, but when it happen =
it=20
  should be a "not good" write response, right?<BR>&nbsp;<BR>Thank you =
and Best=20
  Regards,<BR><BR>Jason HU<BR><BR>
  <HR>
  =D3=C3 Windows Live Spaces =
=D5=B9=CA=BE=B8=F6=D0=D4=D7=D4=CE=D2=A3=AC=D3=EB=BA=C3=D3=D1=B7=D6=CF=ED=C9=
=FA=BB=EE=A3=A1 <A=20
  href=3D"http://spaces.live.com/?page=3DHP" =
target=3D_new>=C1=CB=BD=E2=B8=FC=B6=E0=D0=C5=CF=A2=A3=A1</A>=20
  <P>
  <HR>

  <P></P>_______________________________________________<BR>Ips mailing=20
  =
list<BR>Ips@ietf.org<BR>https://www.ietf.org/mailman/listinfo/ips<BR></BL=
OCKQUOTE></BODY></HTML>

------=_NextPart_000_002A_01C8C732.F388CC20--


--===============0031906969==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips

--===============0031906969==--



From ips-bounces@ietf.org  Fri Jun  6 12:47:03 2008
Return-Path: <ips-bounces@ietf.org>
X-Original-To: ips-archive@optimus.ietf.org
Delivered-To: ietfarch-ips-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 649B03A6D9A;
	Fri,  6 Jun 2008 12:47:03 -0700 (PDT)
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 401AC3A6B39
	for <ips@core3.amsl.com>; Fri,  6 Jun 2008 12:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id d5N7QhS0CC7j for <ips@core3.amsl.com>;
	Fri,  6 Jun 2008 12:47:01 -0700 (PDT)
Received: from outbound-mail-122.bluehost.com (outbound-mail-122.bluehost.com
	[67.222.38.22]) by core3.amsl.com (Postfix) with SMTP id 30CD73A6D83
	for <ips@ietf.org>; Fri,  6 Jun 2008 12:47:01 -0700 (PDT)
Received: (qmail 12224 invoked by uid 0); 6 Jun 2008 19:47:10 -0000
Received: from unknown (HELO box49.bluehost.com) (69.89.20.49)
	by outboundproxy4.bluehost.com with SMTP; 6 Jun 2008 19:47:10 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=weibeltech.com; 
	h=Received:Received:Message-ID:Date:From:To:Subject:MIME-Version:Content-Type:Content-Disposition:Content-Transfer-Encoding:User-Agent:X-Identified-User:DomainKey-Status;
	b=klP+uB2krFMKRct4J1NbmceOXIeZwuH+Y87POQMuOzpZJJPkiCNe0VtxBxL1g9ahcApIO9n1pJGl4KGvsIsoMlMWgflnHCqLi6TF+0IsU39PZ8R/wtGhzTtQTdx9zuNK;
Received: from localhost ([127.0.0.1])
	by box49.bluehost.com with esmtpa (Exim 4.68)
	(envelope-from <david@weibeltech.com>) id 1K4hu2-00043h-CJ
	for ips@ietf.org; Fri, 06 Jun 2008 13:47:10 -0600
Received: from 72.19.152.198 ([72.19.152.198]) by weibeltech.com (Horde
	MIME library) with HTTP; Fri, 06 Jun 2008 13:47:10 -0600
Message-ID: <20080606134710.snbyj2j808cow0g8@weibeltech.com>
Date: Fri, 06 Jun 2008 13:47:10 -0600
From: David Weibel <david@weibeltech.com>
To: ips@ietf.org
MIME-Version: 1.0
Content-Disposition: inline
User-Agent: Internet Messaging Program (IMP) H3 (4.1.6)
X-Identified-User: {1033:box49.bluehost.com:cpanelhorde:box49.bluehost.com}
	{sentby:program running on server}
DomainKey-Status: no signature
Subject: Re: [Ips] OSD over iSCSI (Eddy Quicksall)
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org

> I would like to test my target's support of long CDB's. So I'm
> looking for an iSCSI initiator that will carry long CDB's and
> hopefully an OSD version 2 file system (since OSD issues 200
> byte CDB's).  Does anyone know of anything or work in progress?

The Solaris iSCSI initiator will support long CDBs.  Sun was using
it to test an OSD driver about 3 years ago.  I can dig up more
specifics if your interested.

_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips


From ips-bounces@ietf.org  Fri Jun  6 12:49:39 2008
Return-Path: <ips-bounces@ietf.org>
X-Original-To: ips-archive@optimus.ietf.org
Delivered-To: ietfarch-ips-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C18228C1A3;
	Fri,  6 Jun 2008 12:49:39 -0700 (PDT)
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 77CBA3A6CD1
	for <ips@core3.amsl.com>; Fri,  6 Jun 2008 12:49:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.686
X-Spam-Level: 
X-Spam-Status: No, score=-0.686 tagged_above=-999 required=5 tests=[AWL=1.913, 
	BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id zK20XTGBq0BU for <ips@core3.amsl.com>;
	Fri,  6 Jun 2008 12:49:37 -0700 (PDT)
Received: from fmailhost02.isp.att.net (fmailhost02.isp.att.net
	[207.115.11.52])
	by core3.amsl.com (Postfix) with ESMTP id 868DC3A6DA7
	for <ips@ietf.org>; Fri,  6 Jun 2008 12:49:37 -0700 (PDT)
Received: from ivvtdkv0981 (adsl-218-205-129.jax.bellsouth.net[68.218.205.129])
	by isp.att.net (frfwmhc02) with SMTP
	id <20080606194947H020041jbje>; Fri, 6 Jun 2008 19:49:47 +0000
X-Originating-IP: [68.218.205.129]
Message-ID: <001801c8c80e$79a31f50$0602a8c0@ivivity.com>
From: "Eddy Quicksall" <Quicksall_iSCSI@Bellsouth.net>
To: "David Weibel" <david@weibeltech.com>,
	<ips@ietf.org>
References: <20080606134710.snbyj2j808cow0g8@weibeltech.com>
Date: Fri, 6 Jun 2008 15:49:45 -0400
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [Ips] OSD over iSCSI (Eddy Quicksall)
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org

Yea, if it is open source and there is a download then I would like to try 
it.

Eddy

----- Original Message ----- 
From: "David Weibel" <david@weibeltech.com>
To: <ips@ietf.org>
Sent: Friday, June 06, 2008 3:47 PM
Subject: Re: [Ips] OSD over iSCSI (Eddy Quicksall)


>> I would like to test my target's support of long CDB's. So I'm
>> looking for an iSCSI initiator that will carry long CDB's and
>> hopefully an OSD version 2 file system (since OSD issues 200
>> byte CDB's).  Does anyone know of anything or work in progress?
>
> The Solaris iSCSI initiator will support long CDBs.  Sun was using
> it to test an OSD driver about 3 years ago.  I can dig up more
> specifics if your interested.
>
> _______________________________________________
> Ips mailing list
> Ips@ietf.org
> https://www.ietf.org/mailman/listinfo/ips
> 

_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips


From seungku@fujitsu.com  Sun Jun  8 09:12:14 2008
Return-Path: <seungku@fujitsu.com>
X-Original-To: ietfarch-ips-archive@core3.amsl.com
Delivered-To: ietfarch-ips-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E90E928C11A
	for <ietfarch-ips-archive@core3.amsl.com>; Sun,  8 Jun 2008 09:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.761
X-Spam-Level: 
X-Spam-Status: No, score=-5.761 tagged_above=-999 required=5
	tests=[BAYES_99=3.5, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,
	HTML_MESSAGE=0.001, RAZOR2_CF_RANGE_51_100=0.5,
	RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5,
	RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_XBL=3.033, RDNS_NONE=0.1,
	URIBL_AB_SURBL=10, URIBL_BLACK=20, URIBL_JP_SURBL=10,
	URIBL_OB_SURBL=10, URIBL_RHS_DOB=1.083, URIBL_SBL=20,
	URIBL_SC_SURBL=10, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id l0GdkKTex22q for <ietfarch-ips-archive@core3.amsl.com>;
	Sun,  8 Jun 2008 09:12:14 -0700 (PDT)
Received: from 219-58.static.alkar.net (unknown [213.227.219.58])
	by core3.amsl.com (Postfix) with ESMTP id C960D28C10A
	for <ips-archive@ietf.org>; Sun,  8 Jun 2008 09:12:13 -0700 (PDT)
Date: Sun, 08 Jun 2008 14:25:41 +0000
Message-ID: <47640.keith@lin>
From: "giancarlo wyatt" <seungku@fujitsu.com>
To: <ips-archive@ietf.org>
Subject: 90% lowered prices
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=_HUW0eOQFYCleHB"

This is a multi-part message in MIME format.

--=_HUW0eOQFYCleHB
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

My dear ips-archive, be a smart guy, buy your pills from the most =
well-known shop.
--=_HUW0eOQFYCleHB
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
</HEAD>
<BODY bgColor=3D#66FF99>
<P>My dear ips-archive, be a smart guy, buy your pills from the <A =
HREF=3D"http://mainfollow.com">
most well-known shop.</A></P>



</BODY>
</HTML>
--=_HUW0eOQFYCleHB--




From ips-bounces@ietf.org  Thu Jun 26 14:16:33 2008
Return-Path: <ips-bounces@ietf.org>
X-Original-To: ips-archive@optimus.ietf.org
Delivered-To: ietfarch-ips-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E41053A691D;
	Thu, 26 Jun 2008 14:16:33 -0700 (PDT)
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4DEEE3A691D
	for <ips@core3.amsl.com>; Thu, 26 Jun 2008 14:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level: 
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id OQH3EtO3TkdK for <ips@core3.amsl.com>;
	Thu, 26 Jun 2008 14:16:32 -0700 (PDT)
Received: from fmailhost04.isp.att.net (fmailhost04.isp.att.net
	[204.127.217.104])
	by core3.amsl.com (Postfix) with ESMTP id 9E7103A67EF
	for <ips@ietf.org>; Thu, 26 Jun 2008 14:16:32 -0700 (PDT)
Received: from ivvtdkv0981 (adsl-214-72-41.jax.bellsouth.net[68.214.72.41])
	by isp.att.net (frfwmhc04) with SMTP
	id <20080626211635H04009f5use>; Thu, 26 Jun 2008 21:16:36 +0000
X-Originating-IP: [68.214.72.41]
Message-ID: <002a01c8d7d1$ea76cc90$0602a8c0@ivivity.com>
From: "Eddy Quicksall" <Quicksall_iSCSI@Bellsouth.net>
To: <ips@ietf.org>
Date: Thu, 26 Jun 2008 17:16:35 -0400
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: [Ips] Maximum Burst Size in Disconnect-Reconnect mode page
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1020026071=="
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1020026071==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0027_01C8D7B0.63011390"

This is a multi-part message in MIME format.

------=_NextPart_000_0027_01C8D7B0.63011390
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

In the Disconnect-Reconnect mode page there is a field called MAXIMUM =
BURST SIZE. The rfc does not reference this field but I am wondering if =
the field should be filled with a value computed from the negotiated =
with MaxBurstLength.

Eddy
------=_NextPart_000_0027_01C8D7B0.63011390
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16674" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV><FONT size=3D2>In the Disconnect-Reconnect mode page there is a =
field called=20
MAXIMUM BURST SIZE. The rfc does not reference this field but I am =
wondering if=20
the field should be filled with&nbsp;a value computed from =
the&nbsp;negotiated=20
with MaxBurstLength.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Eddy</FONT></DIV></DIV></BODY></HTML>

------=_NextPart_000_0027_01C8D7B0.63011390--


--===============1020026071==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips

--===============1020026071==--



From ips-bounces@ietf.org  Sat Jun 28 21:49:29 2008
Return-Path: <ips-bounces@ietf.org>
X-Original-To: ips-archive@optimus.ietf.org
Delivered-To: ietfarch-ips-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8F51F3A6A0B;
	Sat, 28 Jun 2008 21:49:29 -0700 (PDT)
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F3BE23A68A3;
	Sat, 28 Jun 2008 21:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id PjgAXOHi0iyS; Sat, 28 Jun 2008 21:49:28 -0700 (PDT)
Received: from mtagate5.de.ibm.com (mtagate5.de.ibm.com [195.212.29.154])
	by core3.amsl.com (Postfix) with ESMTP id C42093A6A0B;
	Sat, 28 Jun 2008 21:49:24 -0700 (PDT)
Received: from d12nrmr1607.megacenter.de.ibm.com
	(d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate5.de.ibm.com (8.13.8/8.13.8) with ESMTP id m5T4mLsa647780;
	Sun, 29 Jun 2008 04:48:21 GMT
Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com
	[9.149.165.228])
	by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v9.0) with
	ESMTP id m5T4mLIL3461300; Sun, 29 Jun 2008 06:48:21 +0200
Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.13.3) with ESMTP
	id m5T4mKC2003229; Sun, 29 Jun 2008 06:48:21 +0200
Received: from d12mc102.megacenter.de.ibm.com (d12mc102.megacenter.de.ibm.com
	[9.149.167.114])
	by d12av02.megacenter.de.ibm.com (8.12.11.20060308/8.12.11) with ESMTP
	id m5T4mKU5003226; Sun, 29 Jun 2008 06:48:20 +0200
In-Reply-To: <002a01c8d7d1$ea76cc90$0602a8c0@ivivity.com>
References: <002a01c8d7d1$ea76cc90$0602a8c0@ivivity.com>
To: "Eddy Quicksall" <Quicksall_iSCSI@Bellsouth.net>
MIME-Version: 1.0
X-KeepSent: B1352BC6:A824EF39-C2257477:0019B399;
 type=4; name=$KeepSent
X-Mailer: Lotus Notes Build VMac_Beta85_20080115_MM2 January 15, 2008
From: Julian Satran <Julian_Satran@il.ibm.com>
Message-ID: <OFB1352BC6.A824EF39-ONC2257477.0019B399-C2257477.001A6596@il.ibm.com>
Date: Sun, 29 Jun 2008 07:48:20 +0300
X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Release 8.0.1|February
	07, 2008) at 29/06/2008 07:48:20,
	Serialize complete at 29/06/2008 07:48:20
Cc: ips@ietf.org, ips-bounces@ietf.org
Subject: Re: [Ips] Maximum Burst Size in Disconnect-Reconnect mode page
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>,
	<mailto:ips-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1203536230=="
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org

This is a multipart message in MIME format.
--===============1203536230==
Content-Type: multipart/alternative; boundary="=_alternative 001A64FFC2257477_="

This is a multipart message in MIME format.
--=_alternative 001A64FFC2257477_=
Content-Type: text/plain; charset="US-ASCII"

Eddy,

The disconnect-reconnect mode page you are referring to is from the FCP 
standard (AFAIK). There are NO mode pages for iSCSI.

Regards,
Julo



From:
"Eddy Quicksall" <Quicksall_iSCSI@Bellsouth.net>
To:
<ips@ietf.org>
Date:
06/27/08 12:18 AM
Subject:
[Ips] Maximum Burst Size in Disconnect-Reconnect mode page



In the Disconnect-Reconnect mode page there is a field called MAXIMUM 
BURST SIZE. The rfc does not reference this field but I am wondering if 
the field should be filled with a value computed from the negotiated with 
MaxBurstLength.
 
Eddy_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips


--=_alternative 001A64FFC2257477_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Eddy,</font>
<br>
<br><font size=2 face="sans-serif">The disconnect-reconnect mode page you
are referring to is from the FCP standard (AFAIK). There are NO mode pages
for iSCSI.</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Julo</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">&quot;Eddy Quicksall&quot; &lt;Quicksall_iSCSI@Bellsouth.net&gt;</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">&lt;ips@ietf.org&gt;</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">06/27/08 12:18 AM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">[Ips] Maximum Burst Size in Disconnect-Reconnect
mode page</font></table>
<br>
<hr noshade>
<br>
<br>
<br><font size=2>In the Disconnect-Reconnect mode page there is a field
called MAXIMUM BURST SIZE. The rfc does not reference this field but I
am wondering if the field should be filled with a value computed from the
negotiated with MaxBurstLength.</font>
<br><font size=3>&nbsp;</font>
<br><font size=2>Eddy</font><tt><font size=2>_______________________________________________<br>
Ips mailing list<br>
Ips@ietf.org<br>
</font></tt><a href=https://www.ietf.org/mailman/listinfo/ips><tt><font size=2>https://www.ietf.org/mailman/listinfo/ips</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
--=_alternative 001A64FFC2257477_=--

--===============1203536230==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips

--===============1203536230==--


