<?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: One stale physikal extend in vg00/lvo2 (swap) in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446546#M656979</link>
    <description>What error did lvsync abort with?&lt;BR /&gt;&lt;BR /&gt;It sounds as though it may be unable to read that extent from the 'good' disk in order to sync it to the new one.&lt;BR /&gt;&lt;BR /&gt;Have you checked for disk errors with one of the STM tools?&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 20 Sep 2000 06:21:38 GMT</pubDate>
    <dc:creator>John Palmer</dc:creator>
    <dc:date>2000-09-20T06:21:38Z</dc:date>
    <item>
      <title>One stale physikal extend in vg00/lvo2 (swap)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446544#M656977</link>
      <description>I got a system with one stale phys. extend in /dev/vg00/lvol2. I replaced the disk and tried to resync using vgsync. This worked for lvol3 but when it came to syncronising lvol2 the command aborted. So I resynced using lvsyn and finaly got all phsyical extends of all lvol?s resynced except of  one physical extend in lvol2. I am totaly confused. Is this caused by the strict allocation policy that needs to be set for swap lvols? Any hints.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;&lt;BR /&gt;Michael Koch</description>
      <pubDate>Wed, 20 Sep 2000 06:10:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446544#M656977</guid>
      <dc:creator>Michael Koch_1</dc:creator>
      <dc:date>2000-09-20T06:10:35Z</dc:date>
    </item>
    <item>
      <title>Re: One stale physikal extend in vg00/lvo2 (swap)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446545#M656978</link>
      <description>I guess the disk which you replaced is the mirror part of root disk/volume group. Did you do a "vgcfgrestore -n /dev/vg00 /dev/dsk/c?t?d?" and "vgchange -a y /dev/vg00" for syncing the root vg data. Could you let us know the procedure you followed?</description>
      <pubDate>Wed, 20 Sep 2000 06:18:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446545#M656978</guid>
      <dc:creator>Vincente Fernandes</dc:creator>
      <dc:date>2000-09-20T06:18:20Z</dc:date>
    </item>
    <item>
      <title>Re: One stale physikal extend in vg00/lvo2 (swap)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446546#M656979</link>
      <description>What error did lvsync abort with?&lt;BR /&gt;&lt;BR /&gt;It sounds as though it may be unable to read that extent from the 'good' disk in order to sync it to the new one.&lt;BR /&gt;&lt;BR /&gt;Have you checked for disk errors with one of the STM tools?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Sep 2000 06:21:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446546#M656979</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2000-09-20T06:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: One stale physikal extend in vg00/lvo2 (swap)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446547#M656980</link>
      <description>&lt;BR /&gt;Yes, are your lvols mirrored ? I would guess so also. If you have an extent which wont resync on say the mirror then this, unfortunately, is not the disk which is faulty, the other (primary) disk is where the fault is. That is the one to replace. The extent is say stale on the mirror disk  but thats because it cant read the corresponding block on the primary disk to copy it (sync it) to the mirror disk. You need to replace the other disk.&lt;BR /&gt;Same thing has happened to me before.&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Sep 2000 06:23:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446547#M656980</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2000-09-20T06:23:00Z</dc:date>
    </item>
    <item>
      <title>Re: One stale physikal extend in vg00/lvo2 (swap)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446548#M656981</link>
      <description>Also run "dd if=/dev/dsk/c?t?d? of=/dev/null bs=4096k" and see if it gives an I/O error. If yes then the disk may have some problems.</description>
      <pubDate>Wed, 20 Sep 2000 06:27:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446548#M656981</guid>
      <dc:creator>Vincente Fernandes</dc:creator>
      <dc:date>2000-09-20T06:27:21Z</dc:date>
    </item>
    <item>
      <title>Re: One stale physikal extend in vg00/lvo2 (swap)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446549#M656982</link>
      <description>Sorry I forgot to mention: vg00 is mirrored and I replaced the disk I assumed to be the one causing problems cause it was the one with the stale extend. I used the following procdeure to get the mirror resynced:&lt;BR /&gt;&lt;BR /&gt;vgcfgbackup vg00&lt;BR /&gt;&lt;BR /&gt;[replace disk]&lt;BR /&gt;&lt;BR /&gt;vgcfgrestore -n /dev/vg00 /dev/rdsk/c0t5d0&lt;BR /&gt;mkboot /dev/rdsk/c0t5d0&lt;BR /&gt;mkboot -a "hpux (;0)/stand/vmunix" /dev/rdsk/c0t5d0&lt;BR /&gt;vgchange -a y /dev/vg00&lt;BR /&gt;vgsync /dev/vg00&lt;BR /&gt;&lt;BR /&gt;cause this resulted in an I/O error after resyncing lvol3 I used lvsync to get the other lvols synced.&lt;BR /&gt;&lt;BR /&gt;syslog states lv_syncx returned error 126.&lt;BR /&gt;&lt;BR /&gt;Using dd on both disk did not result in any error o neither of the disks. &lt;BR /&gt;STM does not list any errors.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I think it realy could turn out that I replaced the wrong disk. Is there any way I can fix this problem without booting the machine into lm mode and using lvreduce -m 0 to get rid of the wrong (not stale) mirror?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Sep 2000 07:08:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/one-stale-physikal-extend-in-vg00-lvo2-swap/m-p/2446549#M656982</guid>
      <dc:creator>Michael Koch_1</dc:creator>
      <dc:date>2000-09-20T07:08:30Z</dc:date>
    </item>
  </channel>
</rss>

