<?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: VA7410  space reservation was desired, but the space left in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/va7410-space-reservation-was-desired-but-the-space-left/m-p/3808673#M20709</link>
    <description>The error in syslog "vmunix: SCSI: Request Timeout; Abort -- lbolt: 1348018328, dev: bc032000, io_id: 303a05f" was due to the VA7410 array slow in responding to I/O request and probably due to lesser space in the array. Putting back the disk to give back some space to the RG should improve the situation.</description>
    <pubDate>Fri, 20 Jul 2007 00:04:22 GMT</pubDate>
    <dc:creator>tkc</dc:creator>
    <dc:date>2007-07-20T00:04:22Z</dc:date>
    <item>
      <title>VA7410  space reservation was desired, but the space left</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7410-space-reservation-was-desired-but-the-space-left/m-p/3808671#M20707</link>
      <description>Hi ALL,&lt;BR /&gt;&lt;BR /&gt; We have RP5405*2(Serviceguard), VA7410, 15*74Gb.&lt;BR /&gt;&lt;BR /&gt;One of 15 disks has yellow indication.&lt;BR /&gt;&lt;BR /&gt;In syslog.log we have a lot of such errors:&lt;BR /&gt;&lt;BR /&gt;vmunix: SCSI: Request Timeout; Abort -- lbolt: 1348018328, dev: bc032000, io_id: 303a05f&lt;BR /&gt;&lt;BR /&gt;armdsp -a &lt;ALIAS&gt;  - see attachment.&lt;BR /&gt;&lt;BR /&gt;All disks have status GOOD, but several from them has warning message :&lt;BR /&gt;&lt;BR /&gt;"  Space is reserved on this disk for subsystem metadata and &lt;BR /&gt;may be a map disk."&lt;BR /&gt;&lt;BR /&gt;At the bottom of armdsp report we can see such message:&lt;BR /&gt;&lt;BR /&gt;"WARNING: The host indicated that hot spare space reservation was desired, but the space left unallocated was insufficient to provide the reservation."&lt;BR /&gt;&lt;BR /&gt;I  read information about this error and &lt;BR /&gt;advice was - add more disks. :)&lt;BR /&gt;&lt;BR /&gt;Any help would be very appreciated,&lt;BR /&gt;Igor.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/ALIAS&gt;</description>
      <pubDate>Tue, 20 Jun 2006 05:32:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7410-space-reservation-was-desired-but-the-space-left/m-p/3808671#M20707</guid>
      <dc:creator>Lemeshko</dc:creator>
      <dc:date>2006-06-20T05:32:51Z</dc:date>
    </item>
    <item>
      <title>Re: VA7410  space reservation was desired, but the space left</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7410-space-reservation-was-desired-but-the-space-left/m-p/3808672#M20708</link>
      <description>Hi Igor, &lt;BR /&gt;&lt;BR /&gt;You have an error with disk M/D15.&lt;BR /&gt;&lt;BR /&gt;Disk at M/D15 is not included at the moment because it was previously used in another array. Did you replace this recently? If you did, you need to tell the array to include this disk and destroy whatever data is on it. This is probably the disk that is showing the amber light. &lt;BR /&gt;&lt;BR /&gt;This will give 73gb back to RG1 and then the status of the array should change from warning to normal again, and the message should dissapear.&lt;BR /&gt;&lt;BR /&gt;I would recommend that you leave some space in the unallocated pool next time you reconfigure the array. This leaves space for the array to perform it's house keeping tasks. I can see that you've got the array in RAID1+0 and that you just have single big luns in each RG, so it may not be possible for you to reduce the size of your luns. In that case, you just need to ensure you monitor the array and respond to any faults promptly.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Owen</description>
      <pubDate>Thu, 19 Jul 2007 11:15:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7410-space-reservation-was-desired-but-the-space-left/m-p/3808672#M20708</guid>
      <dc:creator>Owen_15</dc:creator>
      <dc:date>2007-07-19T11:15:14Z</dc:date>
    </item>
    <item>
      <title>Re: VA7410  space reservation was desired, but the space left</title>
      <link>https://community.hpe.com/t5/disk-enclosures/va7410-space-reservation-was-desired-but-the-space-left/m-p/3808673#M20709</link>
      <description>The error in syslog "vmunix: SCSI: Request Timeout; Abort -- lbolt: 1348018328, dev: bc032000, io_id: 303a05f" was due to the VA7410 array slow in responding to I/O request and probably due to lesser space in the array. Putting back the disk to give back some space to the RG should improve the situation.</description>
      <pubDate>Fri, 20 Jul 2007 00:04:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/va7410-space-reservation-was-desired-but-the-space-left/m-p/3808673#M20709</guid>
      <dc:creator>tkc</dc:creator>
      <dc:date>2007-07-20T00:04:22Z</dc:date>
    </item>
  </channel>
</rss>

