This post is more than 5 years old
2 Intern
•
614 Posts
0
378
October 29th, 2010 12:00
symdev and grp'd and no/grp'd
I ran the symdev -noport -nobcv command and found I had other hypers defined at 27.887 or 27887 MB. They look like are free, however, I noticed some of the hypers have a grp'd attribute. I really do not want to cause any issues while the dmx primary admin is gone on vacatoin and so can anyone tell me what that attribute is about?
Thanks in advance!
Benita
No Events found!
dynamox
9 Legend
•
20.4K Posts
0
October 29th, 2010 12:00
They are part of a device group, they could be clone targets or “reserved” devices for something your symm admin is doing.
dynamox
9 Legend
•
20.4K Posts
0
October 29th, 2010 12:00
they could be, as long as you run -noport ..you know they are not mapped. Let's say you are looking for mirror devices, this is what i would run:
symdev list -sid 1234 -noport -nobcv -raid1 -cap 8632 | grep "N/Grp"
here i am looking for devices that are not mapped, mirrored, not BCV, capacity of ~8.6G and then filter for devices that are not part of any devices group. Now device groups are logical containers that are host specific (unless you use GNS). How many management servers do you use to manage this array ?
admingirl
2 Intern
•
614 Posts
0
October 29th, 2010 12:00
That makes sense she never includes those in the available storage report. Would the devices listed as no/grp'd be allocatable?
admingirl
2 Intern
•
614 Posts
0
October 29th, 2010 13:00
Only one management server and then storage scope which shows different numbers.. If I can use those larger devices 27887 that would be best. My count for 8632 is only 106 which gives me only 2244GB.
admingirl
2 Intern
•
614 Posts
0
October 29th, 2010 13:00
That's great! I executed the command for both hyper sizes 27887 and 8632 and I got a long list of n/grp devices to use.