UNSOLVED

tk_venu

updated

16 years ago

T

tk_venu

1 Rookie

•

82 Posts

0

716

January 4th, 2011 04:00

DATA dev

Hi - in symdev show o/p for below sym Dev's [ex. 094F] show its a DATA dev.

is that mean its a physicall hdd id?

vmax#  symcfg show -pool T2_FC_3R5 -thin -detail -sid xx |more

Symmetrix ID: 00019260xxxx

Symmetrix ID                  : 00019260xxxx

Pool Name                     : T2_FC_3R5

Pool Type                     : Thin

Dev Emulation                 : FBA

Dev Configuration             : RAID-5(3+1)

Pool State                    : Enabled

# of Devices in Pool          : 1400

# of Enabled Devices in Pool  : 1400

Max. Subscription Percent     : 130

Enabled Devices(1400):

  {

   ------------------------------------------------------

   Sym         Total      Alloc       Free Full  Device

   Dev        Tracks     Tracks     Tracks  (%) State

   ------------------------------------------------------

   094F      2209668    1171212    1038456   53  Enabled

   0950      2209668    1168932    1040736   52  Enabled

   0951      2209668    1168452    1041216   52  Enabled

   0952      2209668    1172076    1037592   53  Enabled

  • 279

    0

    Posted January 4th, 2011 07:00

    Data devs are similar to SAVE devices, in that they are not visible to the hosts and must be contained in a pool before they can be used. Thin devices are bind to thin pool which contains data devices.

    In your case, device id 945 is SLV just like other devices and its a logical name for your hyper on the disk.

    Regards,

    Saurabh

  • tk_venu

    1 Rookie

    •

    82 Posts

    279

    0

    Posted January 5th, 2011 03:00

    is that mean... all HDD's hypers are mapped to storage pools as a data/save devs and
    on top on it a logical tdev/vdev will be created, right?

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    279

    1

    Posted January 5th, 2011 04:00

    hypers that comprise TDAT reside on physical drives. Then TDATs as assigned to pools, on top of which you create TDEVs. Here is a 2-way Mirr TDAT ..as you can see it's comprised of two hypers that reside on disk 7B:D0 and 8D:C0

    Back End Disk Director Information
            {
            Hyper Type                             : RAID-1
            Hyper Status                           : Ready           (RW)
            Disk [Director, Interface, TID]        : [N/A,N/A,N/A]
            Disk Director Volume Number            : N/A
            Hyper Number                           : N/A
            Mirror Number                          : 1
            Disk Group Number                      : 1
            Disk Group Name                        : DISK_GROUP_001
            }

        RAID Group Information
            {
            Mirror Number                            : 1
            RAID Type                                : RAID-1
            Device Position                          : Primary
            Protection Level                         : 2
            RAID Group Service State                 : Normal
            Failing Member Mask                      : N/A
            Hyper Devices:
                {
                Device : 00A2
                    {
                    ------------------------------------------------------
                     Disk     DA       Hyper       Member        Disk
                    DA :IT   Vol#   Num Cap(MB)  Num Status  Grp#  Cap(MB)
                    ------------------------------------------------------
                    07B:D0    200     4   67603    1 RW         1   279140
                    08D:C0      4     4   67603    2 RW         1   279140
                    }
                }
            }