SC NAME PLEX CACHE DISKOFFS LENGTH OFF DEVICE MODE SV NAME PLEX VOLNAME NVOLLAYR LENGTH OFF AM/NM MODE SD NAME PLEX DISK DISKOFFS LENGTH OFF DEVICE MODE PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
ST NAME STATE DM_CNT SPARE_CNT APPVOL_CNT Vxdisk list shows: /root # vxdisk listĪ healthy ready for DRD cloning rootdg /root # vxprint -ht -g rootdg However the only thing that actually goes wrong is removing the disk rootdisk02 from the roodg. VxVM vxbrk_rootmir ERROR V-5-2-4020 Attempting to recreate volume meta-data on rootdisk02/c2t0d0 VxVM vxmake ERROR V-5-1-1173 Volume swvol already exists VxVM vxbrk_rootmir INFO V-5-2-2566 14:23: Preparing disk c2t0d0 as a VxVM root disk VxVM vxbrk_rootmir INFO V-5-2-4054 14:23: Setting broken off mirror on c2t0d0 as unique root disk VxVM vxbrk_rootmir INFO V-5-2-4022 14:23: Breaking off root mirror on DA c2t0d0
Sed: Function s/plex=.*$/plex=varvol-02 cannot be parsed. Sed: Function s/plex=.*$/plex=usrvol-02 cannot be parsed. Sed: Function s/plex=.*$/plex=tmpvol-02 cannot be parsed. Sed: Function s/plex=.*$/plex=standvol-02 cannot be parsed.
Sed: Function s/plex=.*$/plex=optvol-02 cannot be parsed. Sed: Function s/plex=.*$/plex=lpvol-02 cannot be parsed. Sed: Function s/plex=.*$/plex=homevol-02 cannot be parsed. VxVM vxbrk_rootmir INFO V-5-2-4052 14:23: Saving configuration data for later restoration VxVM vxbrk_rootmir INFO V-5-2-4025 14:23: DA c2t0d0, DM rootdisk02 is a valid root mirror VxVM vxbrk_rootmir INFO V-5-2-4023 14:23: Checking specified disk(s) for presence and type root # /etc/vx/bin//vxbrk_rootmir -g rootdg -vb rootdisk02 etc/vx/bin//vxbrk_rootmir -g rootdg -vb rootdisk02 If you would rather look smart and say cruise the Internet, do this form. If you want to prove your skills go ahead and use that form and click the link above to find the fix. If you use that form on many HP-UX systems the mirror break will fail and you will have a mess to clean up. etc/vx/bin/vxbrk_rootmir -g rootdg -vb c2t0d0 The man page and HP support says you can use this form. Lets say you want to break c2t0d0 out of the mirror and say make a drd image. root # vxdisk listĬ2t0d0 auto:hpdisk rootdisk02 rootdg onlineĬ2t1d0 auto:hpdisk rootdisk01 rootdg online root # vxedit -g rootdg set failing=off rootdisk02 root # vxedit -g rootdg set failing=off rootdisk01 Easy fix, though I can’t say how long this will last. That being said depending on how you use it, you can have a mess to clean up or not.Ĭ2t0d0 auto:hpdisk rootdisk02 rootdg online failingĬ2t1d0 auto:hpdisk rootdisk01 rootdg online failing The mirror break command is broken on 11.23 and 11.31. This is an improvement to fixing the problems if you do blow things up. This process is experimental and the keywords may be updated as the learning algorithm improves.02 Oct 12 How to not blow up a vxvm boot HP-UX system when breaking the mirror These keywords were added by machine and not by the authors. They are presented in the "Technical Deep Dive" section: subdisk alignment and the infamous "B0" Ghost subdisk (see page 330) that often appears on encapsulated disks. Only two details need further investigation. But the basic steps of this procedure are surprisingly simple, as we will see in this introductory chapter. This procedure is called encapsulation, and you can hear a lot of strange myths about it. Now we turn to a somewhat different procedure to create volumes on already existing application data, so we can move raw device control to VxVM in order to apply all the nice features of an advanced volume management: adding redundancy, resizing, relayouting for performance reasons, online migration to another storage array, etc. Instead we created file systems after volume creation, initialized a starter database, and so on. Of course, there was some kind of data on the disks (any sequence of bits), but we didn’t bother to restore them to an application usable state. So from the application’s point of view, the content of the volumes was uninitialized. Within the previous chapters of this book, we always created volumes based on freshly initialized disks.