4 Beryllium

Re: Allocation queries

Jump to solution

For people happy with UNIX, grep can be handy for you.

root@rox-dev $ symdev -sid 1234 list -identifier device_name -devs 1900:1a0a | grep vSphere

Symmetrix ID: 000192601234

                                  Device

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

Sym  Config          Attr Device Name

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

19F2 TDEV            (M)  vSphere_Prod_Cluster

19FA TDEV            (M)  vSphere_Prod_Cluster

1A02 TDEV            (M)  vSphere_Prod_Cluster

1A0A TDEV            (M)  vSphere_Prod_Cluster

I use this output to check the devices out by name, before performing operations on them.

You can do the same with a simple FOR loop, that lists the identifiers for all devs in a storage group.

Thanks!

7 Thorium

Re: Allocation queries

Jump to solution

Hi Aran,

never considered using that option because most of our boxes are either running SE, inq or we simply rely on the output from PowerPath.  Back in RedHat 4.5 days we actually had some issues where running sympd list would panic the box, so system admin got kind of skittish after that. We since have moved on to RHEL 6.x so it has not been an issue. Just like you i like the inq utility, drop it, make it executable (on *nix) and go ..no need to mess around with solutions enabler.

3 Silver

Re: Allocation queries

Jump to solution

Thanks guys I will try the inq .

0 Kudos
3 Silver

Re: Allocation queries

Jump to solution

I have another question , some what related to this thread .

When a sys admin asks for a disk to be expanded , can we go ahead and expand any lun and then they can allocate it from their end ?

For e.g ,

Hostname : Kronos || D:150 GB || E:1TB||F:500 GB||

Luns created as per inital request

0EFC- 150 GB

0EFD - 1 TB

0EFE- 500 GB .

Now host needs an additional 500 Gigs on D ...

I can expand any dev  ? or I should expand 0EFC only ?

Is there any place where I can read and gain understaning such situations  . Its the most basic thing I should be knowing and I cant seem to get my head around this simple logic ....

Cheers

0 Kudos
7 Thorium

Re: Allocation queries

Jump to solution

it's a one to one relationship (especially on windows with default volume manager). One symmetrix device represents one drive letter on the host side. One some windows systems this could be a mount point.  Does it help ?

0 Kudos
3 Silver

Re: Allocation queries

Jump to solution

If its a one to one relationship then I shoud be expanding the same tdev .

Its always good to check the how  the devs are mapped at the host end . I shouldn't be expanding any devs blindly

is what I get   .

Can multiple devs(meta)  be mapped to a single drive letter ? Let say I have two metaheads 0EFC&0EFE , can they be merged into a single drive .

Want to understand how it works in unix/windows .. I've read about primary/extened /dynamic disks .. 

Thanks Dynamox .

0 Kudos
7 Thorium

Re: Allocation queries

Jump to solution

asceticenergy wrote:

If its a one to one relationship then I shoud be expanding the same tdev .

Its always good to check the how  the devs are mapped at the host end . I shouldn't be expanding any devs blindly

is what I get   .

bingo

asceticenergy wrote:

Can multiple devs(meta)  be mapped to a single drive letter ? Let say I have two metaheads 0EFC&0EFE , can they be merged into a single drive .

Want to understand how it works in unix/windows .. I've read about primary/extened /dynamic disks ..

you can merge them by converting both devices to dynamic drives and then spanning.  I have always hated using dynamic drives on Windows, try to avoid it as the plague.

On *nix platforms don't expand devices, you have very nice logical volume managers so you typically add another device to the operating system and expand the LVM (volume group, logical volume and then the file system)

3 Silver

Re: Allocation queries

Jump to solution

Excellent , thanks again dynamox . I'm good now      .

0 Kudos