<?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: EVA8000: overcommit ==&amp;gt; lost snapshots in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva8000-overcommit-gt-lost-snapshots/m-p/3818312#M20865</link>
    <description>I think what this means is that when you do a snapshot it does not make a copy of the data you are using.  It only makes a copy of the pointers to the data.  Only when you write to the original or snapshot disks does more space actually gets allocated.  If you write a lot of data to the snapshot or original disk then you will chw up a lot of disk space.&lt;BR /&gt;&lt;BR /&gt;You may want to think about using the snapclone instead of the snapshot since that will allocate the space upfront.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Cass</description>
    <pubDate>Mon, 10 Jul 2006 18:55:58 GMT</pubDate>
    <dc:creator>Cass Witkowski</dc:creator>
    <dc:date>2006-07-10T18:55:58Z</dc:date>
    <item>
      <title>EVA8000: overcommit ==&gt; lost snapshots</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva8000-overcommit-gt-lost-snapshots/m-p/3818311#M20864</link>
      <description>All&lt;BR /&gt;&lt;BR /&gt;we've got this event on our SAN:&lt;BR /&gt;"The virtual disk has&lt;BR /&gt;failed. Data was lost because of overcommit. Space efficient snapshot ran out&lt;BR /&gt;of space."&lt;BR /&gt;&lt;BR /&gt;4 snapshots were dropped due to this error. There were no space problemes because there was still 15TB free in this diskgroup.&lt;BR /&gt;&lt;BR /&gt;Does anybody know what's happened or what means 'overcommit' in this situation?&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Jul 2006 03:20:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva8000-overcommit-gt-lost-snapshots/m-p/3818311#M20864</guid>
      <dc:creator>Van Kerckhove Piet</dc:creator>
      <dc:date>2006-07-06T03:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: EVA8000: overcommit ==&gt; lost snapshots</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva8000-overcommit-gt-lost-snapshots/m-p/3818312#M20865</link>
      <description>I think what this means is that when you do a snapshot it does not make a copy of the data you are using.  It only makes a copy of the pointers to the data.  Only when you write to the original or snapshot disks does more space actually gets allocated.  If you write a lot of data to the snapshot or original disk then you will chw up a lot of disk space.&lt;BR /&gt;&lt;BR /&gt;You may want to think about using the snapclone instead of the snapshot since that will allocate the space upfront.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Cass</description>
      <pubDate>Mon, 10 Jul 2006 18:55:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva8000-overcommit-gt-lost-snapshots/m-p/3818312#M20865</guid>
      <dc:creator>Cass Witkowski</dc:creator>
      <dc:date>2006-07-10T18:55:58Z</dc:date>
    </item>
  </channel>
</rss>

