Highlighted

How to change attr

Hi,

We are using Solaris 10; SUN cluster; Veritas Volume Manager and HDS storage with true copy (replication).

Below is the output of "vxdisk -e list":

# vxdisk -e list

DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR       

:

tagmastore-usp1_242a auto:cdsdisk   lmsora-dg01a  lmsora-dg   online               c8t60060E8005654E000000654E0000242Ad0s2 tc-pvol     

tagmastore-usp1_242c auto:cdsdisk   lmsora-dg02a  lmsora-dg   online               c8t60060E8005654E000000654E0000242Cd0s2 std     <------------    

:

 

Query: How to change "std" to "p-vol" in the attr column?

Note: The device has already configured in pair with the secondary.

 

Thanks in advance.

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Hi, managed to bring the attr

Hi,

managed to bring the attr to "p-vol" by using the following command:

vxdisk scandisks

 

Thanks.

View solution in original post

5 Replies
Highlighted
Accepted Solution!

Hi, managed to bring the attr

Hi,

managed to bring the attr to "p-vol" by using the following command:

vxdisk scandisks

 

Thanks.

View solution in original post

Highlighted

Hi, BTW, does it matter if it

Hi,

BTW, does it matter if it is "std" while it should be "p-vol"?

Highlighted

'Extended attributes' are

'Extended attributes' are linked to ASL's that will report device attributes. 

Extract from SF 5.0 MP3 Admin Guide:

 

The following are the list of attributes recognized by Hitachi arrays
 
• STD This is the standard HDS device and is not involved in any special
• PVOL Shadow image primary/original device
• SVOL Shadow image secondary/clone device
• TC-PVOL Truecopy primary/original device
• TC-SVOL Truecopy secondary/clone device
• VVOL Quick shadow device
• HDP Hitachi Dynamic provisioning volume
Highlighted

Hi Marianne, What is the

Hi Marianne,

What is the implication if it shows std but True copy has already been configured from the storage side?

Highlighted

I cannot see that there will

I cannot see that there will be any 'implication'. 
VxVM is simply recognizing what the ASL is reporting.

If changes have been made at array level, a quick rescan (vxdctl enable) should pick up lun attributes.