<?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: extendfs problem on 12H LUNs in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/extendfs-problem-on-12h-luns/m-p/2476303#M688</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The error message means that you have a bad block on the address given.&lt;BR /&gt;&lt;BR /&gt;You can check with the dd command if any errors return:&lt;BR /&gt;dd if=/dev/rdsk/c?t?d? of=/dev/null bs=64k&lt;BR /&gt;if errors replace the disk.&lt;BR /&gt;or you can run a fsck, if not fixed replace the disk.&lt;BR /&gt;&lt;BR /&gt;Good Luck&lt;BR /&gt;</description>
    <pubDate>Fri, 22 Dec 2000 14:08:35 GMT</pubDate>
    <dc:creator>Darrel Louis</dc:creator>
    <dc:date>2000-12-22T14:08:35Z</dc:date>
    <item>
      <title>extendfs problem on 12H LUNs</title>
      <link>https://community.hpe.com/t5/disk-enclosures/extendfs-problem-on-12h-luns/m-p/2476302#M687</link>
      <description>Hello,&lt;BR /&gt;I've a J5600 box connected to AutoRAID12H. Twice I've faced problem in extending the filesystem.&lt;BR /&gt;Event 1. Extension of filesystem within a LUN gave problem. i.e. when&lt;BR /&gt;the VG &amp;amp; LUN were of 20GB, and the LV was extended to 20GB from 10GB. BUT extendfs failed to extended from 10GB to 20GB.&lt;BR /&gt;Event 2. VG was extended beyond a LUN. i.e  when the VG was to be extended&lt;BR /&gt;across the LUNs of 20GB &amp;amp; 10GB. Here too, the extension of VG &amp;amp; LV succeeded&lt;BR /&gt;but extension of filesystem failed.&lt;BR /&gt;&lt;BR /&gt;After executing the extendfs command the display shows all the  alternate superblocks and then gives an error&lt;BR /&gt;&lt;BR /&gt;Read error &lt;BLOCK number=""&gt;&lt;BR /&gt;rdfs: no such device or address&lt;BR /&gt;&lt;BR /&gt;After which lvdisplay contineus to show the size as pre-extension size. &lt;BR /&gt;&lt;BR /&gt;Is the problem due on OS or AutoRAID 12H? Any clue.&lt;/BLOCK&gt;</description>
      <pubDate>Fri, 22 Dec 2000 12:26:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/extendfs-problem-on-12h-luns/m-p/2476302#M687</guid>
      <dc:creator>V Panchapakesan</dc:creator>
      <dc:date>2000-12-22T12:26:56Z</dc:date>
    </item>
    <item>
      <title>Re: extendfs problem on 12H LUNs</title>
      <link>https://community.hpe.com/t5/disk-enclosures/extendfs-problem-on-12h-luns/m-p/2476303#M688</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The error message means that you have a bad block on the address given.&lt;BR /&gt;&lt;BR /&gt;You can check with the dd command if any errors return:&lt;BR /&gt;dd if=/dev/rdsk/c?t?d? of=/dev/null bs=64k&lt;BR /&gt;if errors replace the disk.&lt;BR /&gt;or you can run a fsck, if not fixed replace the disk.&lt;BR /&gt;&lt;BR /&gt;Good Luck&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Dec 2000 14:08:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/extendfs-problem-on-12h-luns/m-p/2476303#M688</guid>
      <dc:creator>Darrel Louis</dc:creator>
      <dc:date>2000-12-22T14:08:35Z</dc:date>
    </item>
    <item>
      <title>Re: extendfs problem on 12H LUNs</title>
      <link>https://community.hpe.com/t5/disk-enclosures/extendfs-problem-on-12h-luns/m-p/2476304#M689</link>
      <description>Hi Darrel,&lt;BR /&gt;I'll check with dd which I've not tried. fsck is ruled out as the filesystem fails while extention, so I don't see a point running fsck. &lt;BR /&gt;No error logs are registered in syslog or EMS. &lt;BR /&gt;bye</description>
      <pubDate>Sat, 23 Dec 2000 04:37:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/extendfs-problem-on-12h-luns/m-p/2476304#M689</guid>
      <dc:creator>V Panchapakesan</dc:creator>
      <dc:date>2000-12-23T04:37:39Z</dc:date>
    </item>
  </channel>
</rss>

