Adding disks into Veritas

From: Wilkinson, Daniel (daniel.wilkinson_at_capgemini.com)
Date: 07/30/04

  • Next message: Chuck: "spare disks on solstice disk suite"
    To: "'sunmanagers@sunmanagers.org'" <sunmanagers@sunmanagers.org>
    Date: Fri, 30 Jul 2004 12:07:31 +0100
    
    

    Hi all,

    We are trying to add a couple of disks into a Veritas disk group, and
    experiencing a few problems..

    Basically, we removed 4 disks from 1 disk group, by removing the volumes on
    them, taking them out of the dg, then offlining them. Then we added them
    into a new (previously existing) dg, onlined them, enabled them. Now we are
    creating a couple of mirror volumes (redo3 and redo4) on them.

    v redo3 fsgen ENABLED ACTIVE 8388608 SELECT -
    pl redo3-01 redo3 ENABLED ACTIVE 8388608 CONCAT -
    RW
    sd sci2db-19-01 redo3-01 sci2db-19 0 8388608 0 c0t0d7
    ENA
    pl redo3-02 redo3 ENABLED ACTIVE 8388608 CONCAT -
    RW
    sd sci2db-21-01 redo3-02 sci2db-21 0 8388608 0 c2t0d7s2
    ENA

    v redo4 fsgen ENABLED ACTIVE 8388608 SELECT -
    pl redo4-01 redo4 ENABLED ACTIVE 8388608 CONCAT -
    RW
    sd sci2db-20-01 redo4-01 sci2db-20 0 8388608 0 c0t0d8s2
    ENA
    pl redo4-02 redo4 ENABLED TEMPRMSD 8388608 CONCAT -
    WO
    sd sci2db-22-01 redo4-02 sci2db-22 0 8388608 0 c2t0d8s2
    ENA

    Ignore the fact the redo is still building in the above output.

    The question is, why is it that only the first desk device has the proper
    short name of c0t0d7, and all the others have got the slice information
    appended to the device name? We added the disks (including re-initializing)
    in exactly the same way for all disks, but no matter how many times we
    remove and re-add these 3 disks, we are getting the longer name. It doesn't
    appear to cause a problem, but we have never seen this anywhere before, and
    don't like the look of it. How can we add the disks and keep to the
    standard disk device naming conventions that don't include the slice info?
    When these disks were in the previous dg they didn't look like this.

    Also, as an aside, when you create a volume that is mirrored from the start,
    why does Veritas choose to make sub volumes, and place the volume on those,
    instead of straight on the disks as it does when you create a standard
    volume, and then mirror it as a separate step?

    Regards

    Dan.

    Our name has changed. Please update your address book to the following format: "recipient@capgemini.com".

    This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers


  • Next message: Chuck: "spare disks on solstice disk suite"

    Relevant Pages

    • Re: High Performance/High Availability SAN config.. Old Skool vs. New School Question..
      ... the time has finally come to upgrade the old SQL Server and SAN. ... > am pretty on top of things as far as how to configure the disks to get the ... > and my Index file groups on different LUNs on the same Disk Group ...
      (microsoft.public.sqlserver.setup)
    • High Performance/High Availability SAN config.. Old Skool vs. New School Question..
      ... the time has finally come to upgrade the old SQL Server and SAN. ... I start to get some information about disks that totally flies ... I come from a mixed background of SQL Server and Oracle, ... and my Index file groups on different LUNs on the same Disk Group ...
      (microsoft.public.sqlserver.setup)
    • Cannot import foreign disks!
      ... I use hard disks to back things up, and plug them in alternately. ... INTERNAL Error - A disk group with the specified name already exists. ... the link provides no help whatsoever. ...
      (microsoft.public.windowsxp.hardware)
    • Cannot import foreign disks!
      ... I use hard disks to back things up, and plug them in alternately. ... INTERNAL Error - A disk group with the specified name already exists. ... the link provides no help whatsoever. ...
      (microsoft.public.windowsxp.general)
    • Cannot import foreign disks!
      ... I use hard disks to back things up, and plug them in alternately. ... INTERNAL Error - A disk group with the specified name already exists. ... the link provides no help whatsoever. ...
      (microsoft.public.windowsxp.help_and_support)