<?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: EVA used sapce in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154792#M42829</link>
    <description>Yes, the EVA knows what blocks have been modified, but as I explained above, when the OS deletes a file, it does not touch the blocks that from the file, only the FAT or MFT, so for the EVA those blocks contain data. So no correlation between what blocks the EVA sees as used and what what the OS sees as used.</description>
    <pubDate>Wed, 04 Feb 2009 21:05:58 GMT</pubDate>
    <dc:creator>Víctor Cespón</dc:creator>
    <dc:date>2009-02-04T21:05:58Z</dc:date>
    <item>
      <title>EVA used sapce</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154788#M42825</link>
      <description>Hi, &lt;BR /&gt;Is there a way of understanding how much space is actually being used on a vdisk as opposed to allocated? I know I could go to the server and try and work this figure out but just wondered if there was a trick to working that out from the EVA perspective. &lt;BR /&gt;&lt;BR /&gt;Thanks in advance, &lt;BR /&gt;Mike</description>
      <pubDate>Wed, 04 Feb 2009 15:25:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154788#M42825</guid>
      <dc:creator>Martin Hodgson</dc:creator>
      <dc:date>2009-02-04T15:25:17Z</dc:date>
    </item>
    <item>
      <title>Re: EVA used sapce</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154789#M42826</link>
      <description>The usage is a filesystem question, the EVA does not know about filesystems, it just uses data blocks.&lt;BR /&gt;As you write and delete files, most blocks will have some data on it, even if it belongs to a deleted file, the EVA does not know that.&lt;BR /&gt;The EVA does not read the MFT, or whatever table the OS uses to keep track of which files are active and which are deleted.</description>
      <pubDate>Wed, 04 Feb 2009 15:32:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154789#M42826</guid>
      <dc:creator>Víctor Cespón</dc:creator>
      <dc:date>2009-02-04T15:32:20Z</dc:date>
    </item>
    <item>
      <title>Re: EVA used sapce</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154790#M42827</link>
      <description>&lt;!--!*#--&gt;Closed</description>
      <pubDate>Wed, 04 Feb 2009 16:04:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154790#M42827</guid>
      <dc:creator>Martin Hodgson</dc:creator>
      <dc:date>2009-02-04T16:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: EVA used sapce</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154791#M42828</link>
      <description>Some storage arrays _do_track the _block_ ranges which have been written at least once and the management tool can show a graphical representation - I've seen it on the HP VA7000 series.&lt;BR /&gt;&lt;BR /&gt;As far as I can tell, the EVA (which shares no development history with the VA7000) does track it, too, in order to optimize CA + BC replication (never-written areas do not get 'copied'), but this information is not accessible (at least by the end-user).</description>
      <pubDate>Wed, 04 Feb 2009 17:54:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154791#M42828</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2009-02-04T17:54:53Z</dc:date>
    </item>
    <item>
      <title>Re: EVA used sapce</title>
      <link>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154792#M42829</link>
      <description>Yes, the EVA knows what blocks have been modified, but as I explained above, when the OS deletes a file, it does not touch the blocks that from the file, only the FAT or MFT, so for the EVA those blocks contain data. So no correlation between what blocks the EVA sees as used and what what the OS sees as used.</description>
      <pubDate>Wed, 04 Feb 2009 21:05:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/eva-used-sapce/m-p/5154792#M42829</guid>
      <dc:creator>Víctor Cespón</dc:creator>
      <dc:date>2009-02-04T21:05:58Z</dc:date>
    </item>
  </channel>
</rss>

