how to remove an abnormal VV? how to recover a inconsistent LD?

[louisji2008]

Hi,

I have a VV which has four LDs, and one of them is in "preserved, checking" state.

Now I'm recover it from the logging LD(pdsld). The time is quite long, it is running for 40 min.

I'm curious, if it failed, how can I remove the VV?

Or is there a command which can drop the preserved data from pdsld or put the LD to the normal state directly without recovery?

[sbhat09]

Hi Louis,

Are you still facing the issie? If yes, can you please share below commands outputs?

showld -vv <vv_name>

showld -d <ld_name>

showld -state <ld_name>

Regards,

Srinivas

[Abdalla1988]

Hello Sir,

Your help is higly appreciated. 

showld -vv xxxxx
Id Name RAID --Detailed_State-- Own SizeMB UsedMB Use Lgct LgId WThru MapV
11 tp-2-sa-0.0 1 normal 1/- 9216 2880 C,SA 0 --- Y Y
12 tp-2-sa-0.1 1 normal 1/- 9216 2880 C,SA 0 --- Y Y
13 tp-2-sd-0.0 5 normal 1/- 258048 240000 C,SD 0 --- Y Y
14 tp-2-sd-0.1 5 checking 1/- 258048 236288 C,SD 0 --- Y Y
15 tp-2-sd-0.2 5 normal 1/- 258048 84864 C,SD 0 --- Y Y
16 tp-2-sd-0.3 5 preserved,checking 1/- 258048 74880 C,SD 0 --- Y Y
17 tp-2-sd-0.4 5 normal 1/- 258048 122240 C,SD 0 --- Y Y
18 tp-2-sd-0.5 5 normal 1/- 258048 126976 C,SD 0 --- Y Y
19 tp-2-sd-0.6 5 normal 1/- 258048 222848 C,SD 0 --- Y Y
20 tp-2-sd-0.7 5 normal 1/- 258048 224256 C,SD 0 --- Y Y
23 tp-2-sd-0.10 5 normal 1/- 258048 245632 C,SD 0 --- Y Y
24 tp-2-sd-0.11 5 normal 1/- 258048 244224 C,SD 0 --- Y Y
25 tp-2-sd-0.12 5 normal 1/- 258048 189824 C,SD 0 --- Y Y
26 tp-2-sd-0.13 5 normal 1/- 258048 197376 C,SD 0 --- Y Y
27 tp-2-sd-0.14 5 normal 1/- 258048 161280 C,SD 0 --- Y Y
28 tp-2-sd-0.15 5 normal 1/- 258048 151936 C,SD 0 --- Y Y
29 tp-2-sd-0.16 5 normal 1/- 258048 131840 C,SD 0 --- Y Y
30 tp-2-sd-0.17 5 normal 1/- 258048 141312 C,SD 0 --- Y Y
35 tp-2-sd-0.18 5 normal 1/- 258048 111360 C,SD 0 --- Y Y
36 tp-2-sd-0.19 5 normal 1/- 258048 136832 C,SD 0 --- Y Y
45 tp-2-sd-0.28 5 normal 1/- 258048 15488 C,SD 0 --- Y Y
46 tp-2-sd-0.29 5 normal 1/- 221184 42496 C,SD 0 --- Y Y
-------------------------------------------------------------------------------------
22 5142528 3107712
 cli% showld -vv APP_Data1
Id Name RAID --Detailed_State-- Own SizeMB UsedMB Use Lgct LgId WThru MapV
11 tp-2-sa-0.0 1 normal 1/- 9216 2880 C,SA 0 --- Y Y
12 tp-2-sa-0.1 1 normal 1/- 9216 2880 C,SA 0 --- Y Y
14 tp-2-sd-0.1 5 checking 1/- 258048 236288 C,SD 0 --- Y Y
15 tp-2-sd-0.2 5 normal 1/- 258048 84864 C,SD 0 --- Y Y
16 tp-2-sd-0.3 5 preserved,checking 1/- 258048 74880 C,SD 0 --- Y Y
18 tp-2-sd-0.5 5 normal 1/- 258048 126976 C,SD 0 --- Y Y
19 tp-2-sd-0.6 5 normal 1/- 258048 222848 C,SD 0 --- Y Y
20 tp-2-sd-0.7 5 normal 1/- 258048 224256 C,SD 0 --- Y Y
22 tp-2-sd-0.9 5 normal 1/- 258048 253568 C,SD 0 --- Y Y
25 tp-2-sd-0.12 5 normal 1/- 258048 189824 C,SD 0 --- Y Y
26 tp-2-sd-0.13 5 normal 1/- 258048 197376 C,SD 0 --- Y Y
27 tp-2-sd-0.14 5 normal 1/- 258048 161280 C,SD 0 --- Y Y
28 tp-2-sd-0.15 5 normal 1/- 258048 151936 C,SD 0 --- Y Y
29 tp-2-sd-0.16 5 normal 1/- 258048 131840 C,SD 0 --- Y Y
30 tp-2-sd-0.17 5 normal 1/- 258048 141312 C,SD 0 --- Y Y
35 tp-2-sd-0.18 5 normal 1/- 258048 111360 C,SD 0 --- Y Y
36 tp-2-sd-0.19 5 normal 1/- 258048 136832 C,SD 0 --- Y Y
42 tp-2-sd-0.25 5 normal 1/- 258048 140160 C,SD 0 --- Y Y
43 tp-2-sd-0.26 5 normal 1/- 258048 52224 C,SD 0 --- Y Y
45 tp-2-sd-0.28 5 normal 1/- 258048 15488 C,SD 0 --- Y Y
-------------------------------------------------------------------------------------
20 4663296 2659072
cli% showld -d tp-2-sd-0.3
Id Name CPG RAID Own SizeMB RSizeMB RowSz StepKB SetSz Refcnt Avail CAvail -----CreationTime------ ----CreationPattern----
16 tp-2-sd-0.3 CPG1_RAID5 5 1/- 258048 344064 1 128 4 0 mag mag 2016-11-04 08:33:02 GMT -p -devtype FC -rpm 10
----------------------------------------------------------------------------------------------------------------------------------------
1 258048 344064
cli% showld -state tp-2-sd-0.3
Id Name -State-- --Detailed_State--
16 tp-2-sd-0.3 degraded preserved,checking
------------------------------------------
1
cli%

[Satish04]

Hi Abdalla1988,

Based on the output you provided, it appears that you have a VV (Virtual Volume) named "APP_Data1" with multiple LDs (Logical Devices).
One of the LDs, specifically "tp-2-sd-0.3," is currently in a degraded state with the state "preserved, checking."

To remove the abnormal VV or recover the inconsistent LD, you can follow these steps:

1. Run the command "showld -state <LD_name>", as you did with "tp-2-sd-0.3" to check the state of the LD.
Ensure that it is in a state that requires recovery or removal.

2. If you want to recover the inconsistent LD, you can run the command "recoverld <LD_name>".
This command initiates the recovery process for the LD and attempts to restore it to a normal state.
The recovery process may take some time to complete.

3.If you want to remove the VV entirely, you can run the command "removevv <VV_name>".
This command removes the VV and all associated LDs. However, please note that removing the VV will result in the loss of all data stored within it.
Ensure you have appropriate backups or have taken necessary precautions before proceeding to remove VV.

Hope this helps.

Regards,
Satish

[Abdalla1988]

Thank you Satish for your reply.

I think the command for recovery is not available in my version as it shows below

cli% showversion
Release version 3.2.1 (MU3)
Patches: P17,P18,P20,P23

Component Name Version
CLI Server 3.2.1 (P20)
CLI Client 3.2.1
System Manager 3.2.1 (P18)
Kernel 3.2.1 (MU3)
TPD Kernel Code 3.2.1 (P17)
TPD Kernel Patch 3.2.1 (P18)

What can I use for this version in order to recover the ld. I have very important data on the vv that requires me to give it a go

[Satish04]

Hi Abdalla1988,

1. Please run the command "startvv -recover <vv_name>" to start the recovery process on a particular VV.
   The recovery process may take some time to complete, depending on the size of the VV.
2. Run the command "setld -recover <ld_name>" to start the recovery process on a particular LD.
   The recovery process may take some time to complete, depending on the size of the LD.

The recovery process of VV or LD should be performed carefully, as it can impact the availability and performance of the storage system.
And it is recommended to contact HPE Tech support for your specific version and configuration to ensure a smooth and successful recovery process.

Note: It is always recommended to have a backup of your data before proceeding recovery process.

Hope this helps.

Regards,
Satish

[Abdalla1988]

Thank you Satish,

Here is the output of the commands

3PAR cli% startvv -recover APP_Data1
startvv: Incorrect number of arguments
SYNTAX
startvv [options] <VV_name>
3PAR cli% help startvv
startvv - Start a virtual volume.

SYNTAX
startvv [options] <VV_name>

DESCRIPTION
The startvv command starts data services on a virtual volume that has not
yet been started.

AUTHORITY
Super, Service
Any role granted the vv_start right

OPTIONS
-ovrd
Specifies that the logical disk is forced to start, even if some
underlying data is missing.

SPECIFIERS
<VV_name>
Specifies the virtual volume name, using up to 31 characters.

NOTES
Access to all domains is required to run this command.

EXAMPLES
None.

3PAR cli% startvv -ovrd APP_Data1
VV APP_Data1 requires ld tp-2-sd-0.3 which is being checked
3PAR cli% setld -recover tp-2-sd-0.3
setld: Invalid argument: -recover

Usage: setld -keep_preserved 0|1 ldname
setld -unpreserve ldname
setld -grow 0|1 ldname
setld -allocate 0|1 ldname

3PAR cli%

3PAR cli% setld -unpreserve tp-2-sd-0.3
setld Error: LD tp-2-sd-0.3 has to be R0 with keep_preserved off

[Satish04]

Hi Abdalla1988,

Can you please try the below commands,

checkvv -y/n -offline <VV name>
checkld –y/n <LD name>
checkld -y/n -p -recover <chunklet ID> <LD name>

But it will take the vv offline to repair if it can and if any data is lost, then you will need to recover from backup.

Note:  If the issue persists,  it is recommended to contact HPE Tech support for your specific version and configuration to ensure a smooth and successful recovery process.

Hope this helps.

Regards,
Satish

[Abdalla1988]

Hello Satish,

The same output

3PAR cli% startvv -ovrd APP_Data1
VV APP_Data1 requires ld tp-2-sd-0.3 which is being checked
3PAR cli% setld -keep_preserved 0 tp-2-sd-0.3
setld Error: LD tp-2-sd-0.3 has preserved data

[Satish04]

Hi Abdalla1988,

Can you please try the below commands,

checkvv -y/n -offline <VV name>
checkld –y/n <LD name>
checkld -y/n -p -recover <chunklet ID> <LD name>

But it will take the vv offline to repair if it can and if any data is lost, then you will need to recover from backup.

Note:  If the issue persists,  it is recommended to contact HPE Tech support for your specific version and configuration to ensure a smooth and successful recovery process.

Hope this helps.

Regards,
Satish

[Abdalla1988]

Satish

I really appreciate your help.

Here the outcome of the commands

3PAR cli% checkvv -y -offline APP_Data1
Specified volumes APP_Data1 will be unavailable during this operation.
Do you want to continue with this operation?
select q=quit y=yes n=no: y
VV APP_Data1 predefined nodes 0x0 should match online nodes 0x2.
3PAR cli% checkld -y tp-2-sd-0.3
Performing a kernel level consistency check, will try to fix inconsistencies
Error: ld tp-2-sd-0.3 has invalid state 3

Errors found

3PAR cli% Error: ld tp-2-sd-0.3 has invalid state 3
invalid command name "Error:

[Satish04]

Hi Abdalla1988,

The error message "ld tp-2-sd-0.3 has invalid state 3" indicates that the LD "tp-2-sd-0.3" is in an invalid state and cannot be recovered using the standard methods.
If the logical disk is in an invalid state, it may require more advanced recovery procedures.

In such cases, I would recommend you contact HPE Tech support with your error message.

Regards,
Satish

[sampiyonts]

Hello friends

Has a solution been found for this situation? We are encountering the same problem