Video Screencast Help

query

Created: 04 Mar 2014 • Updated: 11 Mar 2014 | 3 comments
This issue has been solved. See solution.

hi, I have some questions and I like to see your comment. - I am not able to import an dg and not able to see it with vxprint.How could I recover this dg? - if metadata on an vxvm logical volume is corrupted during the work,or the filesystem is corrupted,then the OS will unmount the filesystem? -when I configure an dg under an HA and this dg is not shared,then is necessary to perform the configuration on master node? -why when there is a need to configure an shared dg,the configuration must be done on master node? tnx a lot, marius

Operating Systems:

Comments 3 CommentsJump to latest comment

Gaurav Sangamnerkar's picture

- I am not able to import an dg and not able to see it with vxprint.How could I recover this dg?

>> You will not see an output in vxpring if dg is not imported. Why dg is not importing could have multiple reasons. Ideally if all disks are available with private region intact, diskgroup should import. Diskgroup can be rebuild using certain outputs like "vxprint -mvphsr, OR VRTS explorer OR /etc/vx/cbr/bk/*.cfgrec"

- if metadata on an vxvm logical volume is corrupted during the work,or the filesystem is corrupted,then the OS will unmount the filesystem?

-- NO, OS will treat it as mounted only however in df conmand you should see "I/O error" on filesystem

-when I configure an dg under an HA and this dg is not shared,then is necessary to perform the configuration on master node?

-- It doesn't matter on which node you are configuring DG into HA however if you are doing any volume manager layer operations, you need to do it on master node (if its a CVM setup). If its plain Storage Foundation (without CVM) , you need to DG operations on node where DG is imported

-why when there is a need to configure an shared dg,the configuration must be done on master node?

-- As explained in previous point, if you have a CVM enabled, diskgroup can be imported on both the nodes at any time, hence all control should be done from one master node. That is why any volume manager layer operations on diskgroup will be done from "master" CVM node.

G

PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
 

SOLUTION
tanislavm's picture

Hi,
So in HA I must to configure dg on master node,regardless that this dg is shared or not.right?

tnx a lot,

marius

TonyGriffiths's picture

Some answers below:

Q1) I am not able to import an dg and not able to see it with vxprint.How could I recover this dg?

TG> Depends, what has happened to the DG and what is the error during the DG import process ?

Q2) if metadata on an vxvm logical volume is corrupted during the work,or the filesystem is corrupted,then the OS will unmount the filesystem?

TG> Possibly, depending on the FS and OS. For example, if VxFS encounters an error on accessing key metadata then it may disable the file system. There are various mount options to control the behavior.

Q3) when I configure an dg under an HA and this dg is not shared,then is necessary to perform the configuration on master node?

TG> If you are using a private disk group (Non-Shared/non-CVM DG), then you can create it and perform admin commands on any node that can access the private DG

Q4) why when there is a need to configure an shared dg,the configuration must be done on master node? 

TG> In earlier versions, when managing CVM/shared diskgroups, you had to do most of the configuration and admin from the master node. In later versions, you should be able to do most commands from the slave nodes via command shipping. What version are you using ?

thanks

tony