This post is more than 5 years old
63 Posts
0
2574
How do I "clear" a diskmark off a volume?
1. Here is the problem:
a. Look at the volumes presented to the NAS:
[nasadmin@uprnas002 nasadmin]$ nas_disk -l
id inuse sizeMB storageID-devID type name servers
1 y 11619 000190101141-063B R1STD root_disk 1,2
2 y 11619 000190101141-063C R1STD root_ldisk 1,2
3 y 2077 000190101141-063D R1STD d3 1,2
4 y 2077 000190101141-063E R1STD d4 1,2
5 y 2077 000190101141-063F R1STD d5 1,2
6 y 2077 000190101141-0640 R1STD d6 1,2
Only 6 "disks", right?
b. But, look at a "probe":
# server_devconfig server_2 -p -s -a
server_2 :
SCSI devices :
chain= 0, scsi-0
stor_id= 000190101141 celerra_id= 000190101141063B
tid/lun= 0/0 type= disk sz= 11619 val= 1 info= 57714163B401SI0063B
tid/lun= 0/1 type= disk sz= 11619 val= 2 info= 57714163C401SI0063C
tid/lun= 0/2 type= disk sz= 2077 val= 3 info= 57714163D401SI0063D
tid/lun= 0/3 type= disk sz= 2077 val= 4 info= 57714163E401SI0063E
tid/lun= 0/4 type= disk sz= 2077 val= 5 info= 57714163F401SI0063F
tid/lun= 0/5 type= disk sz= 2077 val= 6 info= 577141640401SI00640
tid/lun= 0/14 type= disk sz= 2 val= -99 info= 577141040401SI00040 diskerr= unmarked
tid/lun= 0/15 type= disk sz= 1 val= -99 info= 57714163A401SI0063A diskerr= unmarked
tid/lun= 1/0 type= disk sz= 17263 val= 7 info= 5771415C4401SI005C4
tid/lun= 1/1 type= disk sz= 17263 val= 8 info= 5771415C5401SI005C5
tid/lun= 1/2 type= disk sz= 17263 val= 9 info= 5771415C6401SI005C6
tid/lun= 1/3 type= disk sz= 17263 val= 119 info= 5771415C7401SI005C7
2. I actually have more disks presented than DART will add to the "disk table".
o The reason is that volumes 5c4:5c7 were used by a different Celerra before, and have "diskmarks" from that Celerra on them!
o Because my Celerra thinks that they belong to another Celerra, he won't use them....
3. How do I clear the !@#$% diskmarks on volumes 5c4:5c7?
o There doesn't appear to be any command to do this?
4. What do the "force" and "discovery" options do on the "server_devconfig" command:
server_devconfig { | ALL}
|-create -scsi [ ] {-disks | -nondisks | -all}
[-discovery {y|n}] [-monitor {y|n}] [-Force {y|n}]
|-list -scsi [ ] {-disks | -nondisks | -all}
|-probe -scsi [ ] {-disks | -nondisks | -all}
|-rename
Stuart Abramson
Peter_EMC
674 Posts
0
March 4th, 2010 08:00
This primus solution is not for public, sorry.
This is the reason I wrote open an SR and quota the Primus.
This needs to be done BEFORE the lun is removed in the backend.
The diskmark is near the end of the volume, so please use do not use a smaller volume to clone against the diskmarked volume or it will not overwrite the diskmark.
Peter_EMC
674 Posts
0
March 4th, 2010 07:00
from the man page:
[-discovery {y|n}]
Enables or disables the storage discovery operation.
Disabling the -discovery option should only be done under the direction of
an EMC Customer Service Engineer.
[-Force {y|n}]
Overrides the health check failures and changes the storage
configuration.
CAUTION: High availability can be lost when changing the storage
configuration. Changing the storage configuration should only be
done under the direction of an EMC Customer Service Engineer.
StuartA461
63 Posts
0
March 4th, 2010 07:00
Dynamox:
1. I can't figure out how to use "nas_disk -delete dxx -perm" on the "diskmarked" disks, because they don't appear in the "nas_disk -list" table. I don't know what the "dxx" numbers are....
2. But that was smart about the TimeFinder/Clone idea. I can clone copy from a "never-used" HyperVolume to my "diskmarked disks" and wipe out their contents. Then I could discover them again on the NAS and they wouldn't have any diskmarks on them. I'll try that..........
Thanks!
Stuart
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
1
March 4th, 2010 07:00
Stuart,
use "nas_disk -delete dxx -perm" when you reclaim storage from another Celerra. If you already have these symdev , use timefinder/clone or TF/BCV to blow away the content on that disk and then present it to this Celerra.
Message was edited by: dynamox
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
1
March 4th, 2010 07:00
Peter_EMC
674 Posts
1
March 4th, 2010 07:00
Even a client with powerpath would not use this luns.
The normal way for cleaning these diskmarks is while deleting these disks from the nas database using the nas_disk -delete dxx -perm
Another way is a selective VTOC of these Devices.
Or open a NAS SR quoting Primus emc83407, there is a way to delete the diskmark
StuartA461
63 Posts
0
March 4th, 2010 07:00
Peter:
Thanks.
1. How can I use the command:
# nas_disk -delete dxx -perm
when the disks in question don't show up in the nas_disk -l command? What "dxx" number would I use?
2. I will look up that primus....
Stuart
StuartA461
63 Posts
0
March 4th, 2010 07:00
Peter:
I can't find primus emc83407....
StuartA461
63 Posts
0
March 4th, 2010 08:00
Peter:
I just talked to my CE. I mentioned "emc83407". He says he can clear the diskmarks on my volumes. So, I should be good! Thanks for your help!
Stuart Abramson
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
March 4th, 2010 09:00
with Timefinder you can not clone between dissimilar size symdevs.
Peter_EMC
674 Posts
0
March 4th, 2010 22:00
Sorry, but this is not correct,
see Primus emc179141
which shows how "STD volumes may be copied to larger BCVs using symclone by setting an environmental variable"
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
March 5th, 2010 03:00
i am going by what's on page 23, clone device section which says they have to be the same but then on page 37 it says they don't have to. Confusing ..
https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/live1/en_US/Offering_Technical/Technical_Documentation/300-000-876_a12.pdf