Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1832
  • Last Modified:

Veritas /dev/vx/dsk how do I know which FS(s) are created from SANS devices

I have alot of vx file systems mounted and alot of SAN disk .How can I tell which veritas FS(s) are created using SAN disk as opposed to internal NON-SAN disks.
0
FranHill
Asked:
FranHill
1 Solution
 
Darius GhassemCommented:
0
 
FranHillAuthor Commented:
dfshares only shows what file systems are being shared it has nothing to do with physical SAN disk and how they are allocated to veritas file systems
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
FranHillAuthor Commented:
Omar,
Your reference material is useful but still does not answer my question on how i can tell what physical san disk is associated to what volume group.
0
 
omarfaridCommented:
did you have a look at page 77 of the 2nd link where it is showing

vxdisk path | egrep diskname

please see:

http://sfdoccentral.symantec.com/sf/5.0MP3/linux/manpages/vxvm/man1m/vxdisk.html
0
 
FranHillAuthor Commented:
Omar,

Thanks and one additional question: regarding this output
etsis48# vxdisk path | grep hadg48a
c10t50060E800427A450d0s2    GENESIS0_26          hadg48a33    hadg48a      ENABLED
c12t50060E800427A440d0s2    GENESIS0_26          hadg48a33    hadg48a      ENABLED

I can reference the drives  back to the physical drive when I envoke the format command but when I  try to cross reference this drive to iostat -En the device information is truncated.
iostat -En only gives me this portion:
c12t50060E800427A440
Is there away of getting the full output from iostat so I can directly cross
reference to see if the drive is accumulating errors?

Thanks

0
 
FranHillAuthor Commented:
there are several drives in iostat -En that start with

c12t50060E800427A440 but does not give d0 d1 d2 d3 d4 info etc...
0
 
omarfaridCommented:
did you try iostat without -n or with -x ?
0
 
FranHillAuthor Commented:
yes I just tried it and it makes no difference in capturing the complete device name.
0
 
joules17Commented:
hi Franhill,

try
#vxprint -ht

this is give you a list of volumes and the disks used under them,
these volumes are used to mount your file system,
if it is confusing, please paste the vxprint output and I'll explain it to you....


0
 
nyaarCommented:
On my platform is quite simple to tell which disks are from a SAN and  which are not, but this may depend on the san you're using.

IE, the Hitachi ones are the ones on the SAN.

AVAILABLE DISK SELECTIONS:
       0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@0/pci@0/pci@2/scsi@0/sd@0,0
       1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
          /pci@0/pci@0/pci@2/scsi@0/sd@1,0
       2. c2t50060E8003278014d0 <HITACHI-OPEN-V-SUN-2114 cyl 42665 alt 2 hd 15 sec 128>
          /pci@0/pci@0/pci@8/pci@0/pci@2/SUNW,emlxs@0/fp@0,0/ssd@w50060e8003278014,0
       3. c2t50060E8003278014d1 <HITACHI-OPEN-V-SUN-2114 cyl 42665 alt 2 hd 15 sec 128>
          /pci@0/pci@0/pci@8/pci@0/pci@2/SUNW,emlxs@0/fp@0,0/ssd@w50060e8003278014,1


Anyway, you can do this:

1) vxdisk list --> To see which disks vxvm is seeing.

2) vxdisk list <disk>  --> to see disk information

My local disk appear like this:

Device:    c1t0d0s2
devicetag: c1t0d0
type:      auto
info:      format=none
flags:     online ready private autoconfig invalid
pubpaths:  block=/dev/vx/dmp/c1t0d0s2 char=/dev/vx/rdmp/c1t0d0s2
Multipathing information:
numpaths:   1
c1t0d0s2        state=enabled


One of the SAN disks is like this:

Device:    c2t50060E8003278014d0s2
devicetag: c2t50060E8003278014d0
type:      auto
hostid:    myserver <<--- The hostname of the server.
disk:      name=emcpower0 id=1234341450.6.stbic101
group:     name=APLIvg id=1234341512.8.stbic101
info:      format=sliced,privoffset=1,pubslice=4,privslice=3
flags:     online ready private autoconfig autoimport imported
pubpaths:  block=/dev/vx/dmp/c2t50060E8003278014d0s4 char=/dev/vx/rdmp/c2t50060E8003278014d0s4
privpaths: block=/dev/vx/dmp/c2t50060E8003278014d0s3 char=/dev/vx/rdmp/c2t50060E8003278014d0s3
version:   2.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=4 offset=0 len=81911040 disk_offset=5760
private:   slice=3 offset=1 len=3583 disk_offset=1920
update:    time=1236097242 seqno=0.9
ssb:       actual_seqno=0.0
headers:   0 248
configs:   count=1 len=2615
logs:      count=1 len=396
Defined regions:
 config   priv 000017-000247[000231]: copy=01 offset=000000 enabled
 config   priv 000249-002632[002384]: copy=01 offset=000231 enabled
 log      priv 002633-003028[000396]: copy=01 offset=000000 enabled
Multipathing information:
numpaths:   2
c2t50060E8003278014d0s2 state=enabled
c3t50060E8003278004d0s2 state=enabled

Maybe you don't have multipathing, so this output is going to be a little different, at least at the end. But if you take a look, there are a lot of differences between both output ( for example, the hostname of the server that had the disk imported.)

3) When you know which disk is which, you need to map the disk with the volumes. Use  vxprint - Aht  to do this. You would see what Disk group has which disks, and which volumes are contained on it.

Hope this is useful


0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now