<?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: 1 Terabyte DISK Volume for OpenVMS in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107709#M13679</link>
    <description>1 TB (marketing) drives should be well within the limits of OpenVMS, as these drives have capacities below the 1 TB (engineering) limit.&lt;BR /&gt;&lt;BR /&gt;Storage marketing uses base 10 for its calculations of storage capacity.  Storage engineering uses base 2 for its storage capacity addressing.  Why?  For the same actual capacity, the marketing values look better (bigger) than the engineering values, and most (non-nerd) humans deal with base 10 better than base 2.&lt;BR /&gt;&lt;BR /&gt;There can be driver issues; there are ECOs listed in the OpenVMS FAQ for some releases and some drivers.  (In the same section that discusses the terabyte addressing limit.)&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/1" target="_blank"&gt;http://64.223.189.234/node/1&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;There are SATA controllers around which can and do mimic the IDE/ATA controller driver interface; you might find one that works with DQDRIVER.  But you'll slam into the (lack of) 48-bit addressing with this drive.  (I prototyped a DQDRIVER variant with the 48-bit addressing changes, but there's no support for that in any shipping driver nor have there been any plans announced from HP.)&lt;BR /&gt;&lt;BR /&gt;Here's a write-up on IDE/ATA addressing:&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/205" target="_blank"&gt;http://64.223.189.234/node/205&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You might be able to find an UltraSCSI to IDE/ATA adapter; there are a variety of disk adapters available.  Now as to whether or not whatever version of the DKDRIVER SCSI driver can deal with this device (or the adapter), that's another matter.&lt;BR /&gt;&lt;BR /&gt;There are a select few Alpha systems with USB support, and USB can deal with terabyte-scale disks.&lt;BR /&gt;&lt;BR /&gt;Try it.  Let us know.&lt;BR /&gt;</description>
    <pubDate>Thu, 29 Nov 2007 21:18:47 GMT</pubDate>
    <dc:creator>Hoff</dc:creator>
    <dc:date>2007-11-29T21:18:47Z</dc:date>
    <item>
      <title>1 Terabyte DISK Volume for OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107704#M13674</link>
      <description>Is there a way to use 1 TB disk with&lt;BR /&gt;OpenVMS Alpha?&lt;BR /&gt;&lt;BR /&gt;Which firmware, what platform?&lt;BR /&gt;&lt;BR /&gt;I suppose it should be a SCSI disk.&lt;BR /&gt;What about SATA disk?&lt;BR /&gt;</description>
      <pubDate>Mon, 26 Nov 2007 15:54:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107704#M13674</guid>
      <dc:creator>Edmundo T Rodriguez</dc:creator>
      <dc:date>2007-11-26T15:54:39Z</dc:date>
    </item>
    <item>
      <title>Re: 1 Terabyte DISK Volume for OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107705#M13675</link>
      <description>Edmundo,&lt;BR /&gt;&lt;BR /&gt;What is (will) the drive be connected to?&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Mon, 26 Nov 2007 16:07:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107705#M13675</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2007-11-26T16:07:16Z</dc:date>
    </item>
    <item>
      <title>Re: 1 Terabyte DISK Volume for OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107706#M13676</link>
      <description>Edmundo,&lt;BR /&gt;&lt;BR /&gt;  It depends on what you mean. Do you want to take a physical disk drive with a capacity of 1TB or more and connect it to an OpenVMS system? Or, do you want a storage device with capacity over 1TB?&lt;BR /&gt;&lt;BR /&gt;  Both are possible depending on the exact hardware you want.&lt;BR /&gt;&lt;BR /&gt;  A single &amp;gt;1TB drive would need to be on a storage controller capable of partitioning the drive into chucks smaller than 1TB. OpenVMS would see the drive as multiple volumes, each smaller than the OpenVMS 1TB architectural limit for a single physical volume.&lt;BR /&gt;&lt;BR /&gt;  A device larger than 1TB can be created on OpenVMS as a bound volume set (BVS) composed of multiple volumes smaller than 1TB. A BVS may contain up to 256 volumes, so in theory one could create a single disk device of nearly 256TB (but many would question the sanity of anyone contemplating managing such a beast).&lt;BR /&gt;&lt;BR /&gt;  I don't think there are any Alpha systems with SATA controllers. Most Alphas have FibreChannel, SCSI or IDE. On older systems you might find CI, DSSI, or a few other more obscure, and now dead technologies.</description>
      <pubDate>Mon, 26 Nov 2007 17:32:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107706#M13676</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2007-11-26T17:32:28Z</dc:date>
    </item>
    <item>
      <title>Re: 1 Terabyte DISK Volume for OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107707#M13677</link>
      <description>I wanted to take a physical drive of 1 TB and attach it to a Alpha ES47 and or newer architecture like Integrity rx3600 Server.&lt;BR /&gt;&lt;BR /&gt;I suppose the limit you are talking about is on the file system. (Volume per disk)&lt;BR /&gt;&lt;BR /&gt;The idea is that I want to have the less amount of volumes/disk possible for an archive (read only) system.&lt;BR /&gt;&lt;BR /&gt;Naturally the disk will be running in a shadow-set of two at least.</description>
      <pubDate>Wed, 28 Nov 2007 10:31:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107707#M13677</guid>
      <dc:creator>Edmundo T Rodriguez</dc:creator>
      <dc:date>2007-11-28T10:31:11Z</dc:date>
    </item>
    <item>
      <title>Re: 1 Terabyte DISK Volume for OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107708#M13678</link>
      <description>&lt;BR /&gt;Well, as long as the drive presents itself with less than 2**31 sectors it should be fine:&lt;BR /&gt;&lt;BR /&gt;$ x=%x7fffffff&lt;BR /&gt;$ shwo symb x&lt;BR /&gt;  X = 2147483647   Hex = 7FFFFFFF  Octal = 17777777777&lt;BR /&gt;&lt;BR /&gt;So if I look at an example "Seagate 1Tb Barracuda ES.2"&lt;BR /&gt;&lt;BR /&gt;The detailed specs give:&lt;BR /&gt;Guaranteed Sectors = 1,953,525,168  &lt;BR /&gt;&lt;BR /&gt;So that's well under 1024*1024*1024*2&lt;BR /&gt;&lt;BR /&gt;Enjoy,&lt;BR /&gt;Hein.&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Nov 2007 10:54:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107708#M13678</guid>
      <dc:creator>Hein van den Heuvel</dc:creator>
      <dc:date>2007-11-28T10:54:03Z</dc:date>
    </item>
    <item>
      <title>Re: 1 Terabyte DISK Volume for OpenVMS</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107709#M13679</link>
      <description>1 TB (marketing) drives should be well within the limits of OpenVMS, as these drives have capacities below the 1 TB (engineering) limit.&lt;BR /&gt;&lt;BR /&gt;Storage marketing uses base 10 for its calculations of storage capacity.  Storage engineering uses base 2 for its storage capacity addressing.  Why?  For the same actual capacity, the marketing values look better (bigger) than the engineering values, and most (non-nerd) humans deal with base 10 better than base 2.&lt;BR /&gt;&lt;BR /&gt;There can be driver issues; there are ECOs listed in the OpenVMS FAQ for some releases and some drivers.  (In the same section that discusses the terabyte addressing limit.)&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/1" target="_blank"&gt;http://64.223.189.234/node/1&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;There are SATA controllers around which can and do mimic the IDE/ATA controller driver interface; you might find one that works with DQDRIVER.  But you'll slam into the (lack of) 48-bit addressing with this drive.  (I prototyped a DQDRIVER variant with the 48-bit addressing changes, but there's no support for that in any shipping driver nor have there been any plans announced from HP.)&lt;BR /&gt;&lt;BR /&gt;Here's a write-up on IDE/ATA addressing:&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/205" target="_blank"&gt;http://64.223.189.234/node/205&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You might be able to find an UltraSCSI to IDE/ATA adapter; there are a variety of disk adapters available.  Now as to whether or not whatever version of the DKDRIVER SCSI driver can deal with this device (or the adapter), that's another matter.&lt;BR /&gt;&lt;BR /&gt;There are a select few Alpha systems with USB support, and USB can deal with terabyte-scale disks.&lt;BR /&gt;&lt;BR /&gt;Try it.  Let us know.&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Nov 2007 21:18:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/1-terabyte-disk-volume-for-openvms/m-p/4107709#M13679</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2007-11-29T21:18:47Z</dc:date>
    </item>
  </channel>
</rss>

