Re: [Q] Rootvg VGDA bad block???

From: John Jolet (john.jolet_at_FXFN.COM)
Date: 07/16/03

  • Next message: N. Leenders: "console"
    Date:         Wed, 16 Jul 2003 14:25:42 -0500
    To: aix-l@Princeton.EDU
    
    

    that's the trade-off. this way you can totally script it if youwant, but you have a period where you are exposed with no mirror.

    -----Original Message-----
    From: Adams Kevin J [mailto:kevin.adams@PHS.COM]
    Sent: Wednesday, July 16, 2003 2:15 PM
    To: aix-l@Princeton.EDU
    Subject: Re: [Q] Rootvg VGDA bad block???

    I guess I've always run mkszfile and doctored the /image.data file and then
    run mksysb without the -i for those situations.
    Kevin

    -----Original Message-----
    From: John Jolet [mailto:john.jolet@FXFN.COM]
    Sent: Wednesday, July 16, 2003 11:10 AM
    To: aix-l@Princeton.EDU
    Subject: Re: [aix-l] [Q] Rootvg VGDA bad block???

    one reason might be that if you make a makesysb with the mirror on, and
    restore it to a single-disk box, it'll create both copies on the same hdisk,
    which requires twice the disk space to succeed, of course. if you break
    them mirror, take a makesysb, then restore the mirror, you have the option
    of restoring the makesysb to a smaller box.

    -----Original Message-----
    From: Adams Kevin J [mailto:kevin.adams@PHS.COM]
    Sent: Wednesday, July 16, 2003 12:39 PM
    To: aix-l@Princeton.EDU
    Subject: Re: [Q] Rootvg VGDA bad block???

    Why are you breaking the mirror to do a mksysb backup in the first place?
    Kevin Adams
    PacifiCare Behavioral Health
    Principal Systems Analyst
    AIX Certified Advanced Technical Expert

    -----Original Message-----
    From: leed@CHELE.CAIS.NET [mailto:leed@CHELE.CAIS.NET]
    Sent: Tuesday, July 15, 2003 5:17 AM
    To: aix-l@Princeton.EDU
    Subject: [aix-l] [Q] Rootvg VGDA bad block???

    We have AIX 4.3.3 on S7A. Normally the "rootvg" is mirror (hdisk0 and
    hdisk1). Every time we doing "mksysb", we break the mirror and make
    backup. unfortunately, after we break the mirror, their has "0516-086
    lsvg: Volume group descriptor area has a bad block." message happen. My
    questions are:

    1. does their has way to fix this problem withour re-install?

    2. can I boot from hdisk1 (mirror already break)?

    3. any other suggestion?

    Thanks.

    other info. for you to reference:

    % lsvg rootvg
    0516-086 lsvg: Volume group descriptor area has a bad block.
    VOLUME GROUP: rootvg VG IDENTIFIER: 000929250b12d3e5
    VG STATE: active PP SIZE: 16 megabyte(s)
    VG PERMISSION: read/write TOTAL PPs: ???????
    MAX LVs: 256 FREE PPs: 206 (3296
    megabytes)
    LVs: 9 USED PPs: ???????
    OPEN LVs: 8 QUORUM: 2
    TOTAL PVs: 1 VG DESCRIPTORS: 2
    STALE PVs: ??????? STALE PPs: ???????
    ACTIVE PVs: ??????? AUTO ON: yes
    MAX PPs per PV: 1016 MAX PVs: 32
    %

    % lspv hdisk0
    PHYSICAL VOLUME: hdisk0 VOLUME GROUP: rootvg
    PV IDENTIFIER: 0009292500383f27 VG IDENTIFIER 000929250b12d3e5
    PV STATE: active
    STALE PARTITIONS: 0 ALLOCATABLE: yes
    PP SIZE: 16 megabyte(s) LOGICAL VOLUMES: 9
    TOTAL PPs: 542 (8672 megabytes) VG DESCRIPTORS: 2
    FREE PPs: 206 (3296 megabytes)
    USED PPs: 336 (5376 megabytes)
    FREE DISTRIBUTION: 45..01..00..51..109
    USED DISTRIBUTION: 64..107..108..57..00

    This electronic message transmission, including any attachments, contains
    information from PacifiCare Health Systems Inc. which may be confidential or
    privileged. The information is intended to be for the use of the individual
    or entity named above. If you are not the intended recipient, be aware that
    any disclosure, copying, distribution or use of the contents of this
    information is prohibited.

    If you have received this electronic transmission in error, please notify
    the sender immediately by a "reply to sender only" message and destroy all
    electronic and hard copies of the communication, including attachments.

    This electronic message transmission, including any attachments, contains information from PacifiCare Health Systems Inc. which may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited.

    If you have received this electronic transmission in error, please notify the sender immediately by a "reply to sender only" message and destroy all electronic and hard copies of the communication, including attachments.


  • Next message: N. Leenders: "console"

    Relevant Pages

    • Re: Re-mirroring rootvg
      ... that we're sure all is well, we need to re-mirror rootvg again. ... I use the following commands if both disk have the same size and the ... Mirror rootvg using mirrorvg or mklvcopy. ...
      (comp.unix.aix)
    • stale root partiition - AIX 5.3
      ... to take effect for rootvg. ... 0516-1135 unmirrorvg: The unmirror of the volume group failed. ... shows 88 stale partitions - which is the amount of partitions for /. ... mirror is apparently stale. ...
      (comp.unix.aix)
    • Re: Question on unmirroring rootvg before mksysb
      ... So short of a customized image.data file, the rootvg will be ... you can customize the image.data file to ... restore it without a mirror. ... During he restore you can use a customized image.data file to ...
      (AIX-L)
    • HELP - stale partitions
      ... Last week "stale partition" messages began to appear for all rootvg lv's, and err msgs about hdisk0. ... Then we replaced hdisk0 after breaking the mirror, hoping to remirror after adding the new hdisk0 to rootvg. ... 9D035E4D 1214165306 P S SYSVMM DATA STORAGE INTERRUPT, ...
      (AIX-L)
    • Re: HELP - stale partitions
      ... Last week "stale partition" messages began to appear for all ... and err msgs about hdisk0. ... we tried to unmirror and then mirror rootvg. ... Then we replaced hdisk0 after breaking the mirror, ...
      (AIX-L)