<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Introduction to iSCSI</title>
	<atom:link href="http://www.linux-mag.com/id/7605/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.linux-mag.com/id/7605/</link>
	<description>Open Source, Open Standards</description>
	<lastBuildDate>Sat, 05 Oct 2013 13:48:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: piavka</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7367</link>
		<dc:creator>piavka</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7367</guid>
		<description>&lt;p&gt;I can\&#039;t believe that you mixed the iscsi initiator and target roles - this is shame to have such a dummy and miss informative article on linux-mag.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I can\&#8217;t believe that you mixed the iscsi initiator and target roles &#8211; this is shame to have such a dummy and miss informative article on linux-mag.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jsoda</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7368</link>
		<dc:creator>jsoda</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7368</guid>
		<description>&lt;p&gt;seriously?  an article on iscsi that mixes up target and initiator?  wow.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>seriously?  an article on iscsi that mixes up target and initiator?  wow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: laytonjb</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7369</link>
		<dc:creator>laytonjb</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7369</guid>
		<description>&lt;p&gt;Mea maxima culpa. I always get the initiator and target backwards. I have fixed the text and will fix Figure 3 in a few hours.&lt;/p&gt;
&lt;p&gt;I have also changed the wording in a few places where it wasn\&#039;t as accurate as it should have been.&lt;/p&gt;
&lt;p&gt;Jeff
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Mea maxima culpa. I always get the initiator and target backwards. I have fixed the text and will fix Figure 3 in a few hours.</p>
<p>I have also changed the wording in a few places where it wasn\&#8217;t as accurate as it should have been.</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: viralnexxus</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7370</link>
		<dc:creator>viralnexxus</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7370</guid>
		<description>&lt;p&gt;I think Jeff did a great job on introducing me to iSCSI and SANS.  Mistakes will always be made, but bashing him sarcastically instead of correcting him politely shows a serious lack of class.  Just my opinion.&lt;/p&gt;
&lt;p&gt;-Victor
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I think Jeff did a great job on introducing me to iSCSI and SANS.  Mistakes will always be made, but bashing him sarcastically instead of correcting him politely shows a serious lack of class.  Just my opinion.</p>
<p>-Victor</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: normalex</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7371</link>
		<dc:creator>normalex</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7371</guid>
		<description>&lt;p&gt;100% agree with viralnexxus.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>100% agree with viralnexxus.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dotcomstu</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7372</link>
		<dc:creator>dotcomstu</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7372</guid>
		<description>&lt;p&gt;What happens if the SAN dies?&lt;/p&gt;
&lt;p&gt;This setup would benefit from having a DRBD network mirror to remove the single point of failure introduced by having all servers depending on the one SAN machine: http://www.drbd.org/
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>What happens if the SAN dies?</p>
<p>This setup would benefit from having a DRBD network mirror to remove the single point of failure introduced by having all servers depending on the one SAN machine: <a href="http://www.drbd.org/" rel="nofollow">http://www.drbd.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chammitt</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7373</link>
		<dc:creator>chammitt</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7373</guid>
		<description>&lt;p&gt;also, you would typically want to have a separate Ethernet Network (for SAN) from your traditional Ethernet Network (for other IP traffic) for performance reasons...not just one Ethernet Network.  While possible to vlan it out...if you have decent any amount of workload, your performance will suffer.  But then again, if you are planning to use 2TB+ SATA drives...this might not be an issue for you.  I\&#039;d stick to the 300-450GB SAS drives personally.  spindle &gt; capacity less you are doing a huge sequential workload....which most people do not!
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>also, you would typically want to have a separate Ethernet Network (for SAN) from your traditional Ethernet Network (for other IP traffic) for performance reasons&#8230;not just one Ethernet Network.  While possible to vlan it out&#8230;if you have decent any amount of workload, your performance will suffer.  But then again, if you are planning to use 2TB+ SATA drives&#8230;this might not be an issue for you.  I\&#8217;d stick to the 300-450GB SAS drives personally.  spindle &gt; capacity less you are doing a huge sequential workload&#8230;.which most people do not!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zodilib</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7374</link>
		<dc:creator>zodilib</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7374</guid>
		<description>&lt;p&gt;I liked the article. However would love to know more about the initiator and adaptor story. Meanwhile please let me know if the network is geographically scattered can we still have a FC NAS setup ? My question must be dump,, forgive me I am just starting :)
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I liked the article. However would love to know more about the initiator and adaptor story. Meanwhile please let me know if the network is geographically scattered can we still have a FC NAS setup ? My question must be dump,, forgive me I am just starting :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: laytonjb</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7375</link>
		<dc:creator>laytonjb</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7375</guid>
		<description>&lt;p&gt;@dotcomstu,&lt;/p&gt;
&lt;p&gt;If the SAN dies, then you lose storage. Using DRDB is an option, but it\&#039;s basically having a second network. So you could have a second SAN and achieve similar results (price and performance are TBD). But it is an option and an interesting one.&lt;/p&gt;
&lt;p&gt;Jeff
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@dotcomstu,</p>
<p>If the SAN dies, then you lose storage. Using DRDB is an option, but it\&#8217;s basically having a second network. So you could have a second SAN and achieve similar results (price and performance are TBD). But it is an option and an interesting one.</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: laytonjb</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7376</link>
		<dc:creator>laytonjb</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7376</guid>
		<description>&lt;p&gt;@chammitt,&lt;/p&gt;
&lt;p&gt;A very valid point about having 2 ethernet networks either physical or VLAN. I think there are two camps arguing this point. One camp wants a single big pipe for all traffic (call this the 10GigE camp) and the second camp wants a bit more redundancy and segregation of traffic. I don\&#039;t think there is one right answer and depends upon the workload, the risk, and the desire (or need) for redundancy.&lt;/p&gt;
&lt;p&gt;Personally, while the single (fat) line is very appealing, I would also like to have at least 1 GigE line to each server for other tasks (monitoring, imaging, etc.). As you point out, it helps reduce traffic on the iSCSI line. GigE isn\&#039;t expensive so I don\&#039;t see it being a problem overall. Plus, you could do multi-pathing across both lines recognizing the difference in performance.&lt;/p&gt;
&lt;p&gt;Jeff
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@chammitt,</p>
<p>A very valid point about having 2 ethernet networks either physical or VLAN. I think there are two camps arguing this point. One camp wants a single big pipe for all traffic (call this the 10GigE camp) and the second camp wants a bit more redundancy and segregation of traffic. I don\&#8217;t think there is one right answer and depends upon the workload, the risk, and the desire (or need) for redundancy.</p>
<p>Personally, while the single (fat) line is very appealing, I would also like to have at least 1 GigE line to each server for other tasks (monitoring, imaging, etc.). As you point out, it helps reduce traffic on the iSCSI line. GigE isn\&#8217;t expensive so I don\&#8217;t see it being a problem overall. Plus, you could do multi-pathing across both lines recognizing the difference in performance.</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: laytonjb</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7377</link>
		<dc:creator>laytonjb</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7377</guid>
		<description>&lt;p&gt;@zodilib,&lt;/p&gt;
&lt;p&gt;The story behind initiator and target is that I got them backwards in the original post of the article. I think I fixed everything.&lt;/p&gt;
&lt;p&gt;To be honest, I don\&#039;t know enough about FC to know if you can run it over long distances. I\&#039;m assuming there are companies that have WAN FC products (there are companies that do this for InfiniBand so I\&#039;m assuming FC is the same).&lt;/p&gt;
&lt;p&gt;Jeff
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@zodilib,</p>
<p>The story behind initiator and target is that I got them backwards in the original post of the article. I think I fixed everything.</p>
<p>To be honest, I don\&#8217;t know enough about FC to know if you can run it over long distances. I\&#8217;m assuming there are companies that have WAN FC products (there are companies that do this for InfiniBand so I\&#8217;m assuming FC is the same).</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: piavka</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7378</link>
		<dc:creator>piavka</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7378</guid>
		<description>&lt;p&gt;@viralnexxus,&lt;/p&gt;
&lt;p&gt;IMHO mixing such fundamental things as iscsi initiator and target (not just in accidentalt in one place but overall in all article including the diagram) in 99% of cases indicates that the author is familiar with the subject only theoretically. I think that anyone who have actually made the simplest iscsi setup even just once, would not mix such things - but there can be exceptions of course.&lt;/p&gt;
&lt;p&gt;My point is that I expect the author of the article not to be a novice in a subject he/she is writing about and at least have some real practical experience with the subject, also considering that it\&#039;s posted not on authors personal blog but in a well known magazine where people reading it have certain expectations from the articles. And I don\&#039;t mind if the article is introduction, intermediate or expert level - as long as it is fundamentally correct, while minor mistakes I\&#039;m fine with of course.&lt;/p&gt;
&lt;p&gt;I\&#039;m sorry for such a response ,I should have been much more polite,&lt;br /&gt;
but honestly I never remember myself of ever writing such a bashing comment before.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@viralnexxus,</p>
<p>IMHO mixing such fundamental things as iscsi initiator and target (not just in accidentalt in one place but overall in all article including the diagram) in 99% of cases indicates that the author is familiar with the subject only theoretically. I think that anyone who have actually made the simplest iscsi setup even just once, would not mix such things &#8211; but there can be exceptions of course.</p>
<p>My point is that I expect the author of the article not to be a novice in a subject he/she is writing about and at least have some real practical experience with the subject, also considering that it\&#8217;s posted not on authors personal blog but in a well known magazine where people reading it have certain expectations from the articles. And I don\&#8217;t mind if the article is introduction, intermediate or expert level &#8211; as long as it is fundamentally correct, while minor mistakes I\&#8217;m fine with of course.</p>
<p>I\&#8217;m sorry for such a response ,I should have been much more polite,<br />
but honestly I never remember myself of ever writing such a bashing comment before.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bobgjunga</title>
		<link>http://www.linux-mag.com/id/7605/#comment-7379</link>
		<dc:creator>bobgjunga</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/7605/#comment-7379</guid>
		<description>&lt;p&gt;What about the difference in latency between FC and GigE? 10 GigE? I think that bandwidth determines how many severs you can have on a SAN without performance degradation but latency limits the maximum single server performance. &lt;/p&gt;
&lt;p&gt;So what is the performance comparison of having a MySQL data folder on..&lt;/p&gt;
&lt;li&gt;a local 15k rpm SAS dirve&lt;/li&gt;
&lt;li&gt;a FC SAN drive &lt;/li&gt;
&lt;li&gt;a 15k rpm SAS dirve over a 1 GigE iSCSI SAN&lt;/li&gt;
&lt;p&gt;--BobG
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>What about the difference in latency between FC and GigE? 10 GigE? I think that bandwidth determines how many severs you can have on a SAN without performance degradation but latency limits the maximum single server performance. </p>
<p>So what is the performance comparison of having a MySQL data folder on..</p>
<li>a local 15k rpm SAS dirve</li>
<li>a FC SAN drive </li>
<li>a 15k rpm SAS dirve over a 1 GigE iSCSI SAN</li>
<p>&#8211;BobG</p>
]]></content:encoded>
	</item>
</channel>
</rss>