<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Hello All, in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Hello-All/m-p/42855#M3948</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Replying back to add further details in the event this thread is found in the future.&amp;nbsp; A lun, while being a "disk" to a client that's connected to it, is just a file (using that very loosely here) on the volume itself.&amp;nbsp; A share just exposes the volume to CIFS, making the volume capable of storing / accessing files over the CIFS protocol.&amp;nbsp; So you can certainly have a volume that is used for both SAN or NAS (CIFS).&amp;nbsp; HOWEVER, it's not recommended that you do that.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a Best Practice you should use volumes housing LUNs only for SAN traffic and volumes for NAS related traffic only for NAS.&amp;nbsp; Among other things, there is the issue of space accounting and space reservations that come into play for LUNs and if you are storing non-SAN data on the same volume as your NAS data it will make space accounting a nightmare&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Dec 2013 19:42:03 GMT</pubDate>
    <dc:creator>waldrop</dc:creator>
    <dc:date>2013-12-10T19:42:03Z</dc:date>
    <item>
      <title>Hello All,</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Hello-All/m-p/42842#M3943</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG style="color: #280df1; font-size: 12pt; font-family: trebuchet ms,geneva;"&gt;Is it possible to create SAN LUN &amp;amp; NAS Share for a single volume?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="color: #280df1; font-size: 12pt; font-family: trebuchet ms,geneva;"&gt;If yes please explain me.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="color: #280df1; font-size: 12pt; font-family: trebuchet ms,geneva;"&gt;Thank in Advance.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:13:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Hello-All/m-p/42842#M3943</guid>
      <dc:creator>RAGHU2PRASAD</dc:creator>
      <dc:date>2025-06-05T06:13:34Z</dc:date>
    </item>
    <item>
      <title>Re: Hello All,</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Hello-All/m-p/42847#M3945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, it is possible - but not recommended.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You just create a volume &amp;amp; LUN inside it. Then you can either share/export the entire volume (so you will see your LUN as a big file from a CIFS/NFS client), or create a qtree (think a folder) &amp;amp; share/export it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Radek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Dec 2012 10:27:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Hello-All/m-p/42847#M3945</guid>
      <dc:creator>radek_kubka</dc:creator>
      <dc:date>2012-12-19T10:27:22Z</dc:date>
    </item>
    <item>
      <title>Re: Hello All,</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Hello-All/m-p/42852#M3947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your reply Radek. My question is like LUN environment is entire different from CIFS environment. Then how it is possible for single volume providing LUN as well Share.&lt;/P&gt;&lt;P&gt;The volume should be either NAS or SAN environment. If the Volume is in NAS we can't create LUN or if volume is in SAN we can't create share. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please correct me if I am wrong.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Dec 2012 12:29:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Hello-All/m-p/42852#M3947</guid>
      <dc:creator>RAGHU2PRASAD</dc:creator>
      <dc:date>2012-12-19T12:29:12Z</dc:date>
    </item>
    <item>
      <title>Re: Hello All,</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Hello-All/m-p/42855#M3948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Replying back to add further details in the event this thread is found in the future.&amp;nbsp; A lun, while being a "disk" to a client that's connected to it, is just a file (using that very loosely here) on the volume itself.&amp;nbsp; A share just exposes the volume to CIFS, making the volume capable of storing / accessing files over the CIFS protocol.&amp;nbsp; So you can certainly have a volume that is used for both SAN or NAS (CIFS).&amp;nbsp; HOWEVER, it's not recommended that you do that.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a Best Practice you should use volumes housing LUNs only for SAN traffic and volumes for NAS related traffic only for NAS.&amp;nbsp; Among other things, there is the issue of space accounting and space reservations that come into play for LUNs and if you are storing non-SAN data on the same volume as your NAS data it will make space accounting a nightmare&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Dec 2013 19:42:03 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Hello-All/m-p/42855#M3948</guid>
      <dc:creator>waldrop</dc:creator>
      <dc:date>2013-12-10T19:42:03Z</dc:date>
    </item>
  </channel>
</rss>

