- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Questions about checkld recover LD
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2020 11:17 PM
тАО10-02-2020 11:17 PM
Questions about checkld recover LD
1. Is the recover speed normal?
2. How can I know the number of chunklets need to be recovered?
3. After checkld finished, should I execute checkvv?
4. How to resolve the question: I've run checkvv, the showtask displayed "There is no SA/SD space for volume xxx", then the command just finished.
How time flies~~~
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2020 02:13 AM
тАО10-05-2020 02:13 AM
Re: Questions about checkld recover LD
Hi Louis,
Are you still facing the issue? If yes, please if the below is useful for you:
1. 12 hours is not the ideal time it may take. It is longer than normal for the task.
2. YOu may verify with checkld -progress
3. After finishing checkld, you can validate with showld -vv <vv_name>
4. Can you please share the complete command output for showtask -d <task_id>
Regards,
Srinivas
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2020 08:08 PM
тАО10-05-2020 08:08 PM
Re: Questions about checkld recover LD
Hi,
here are the shwold commands.
How time flies~~~
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-05-2020 08:16 PM
тАО10-05-2020 08:16 PM
Re: Questions about checkld recover LD
Before run the checkld -y -progress -recover command, I found the state of a chunlet 364:504 is "logging", as all the others are normal:
60 0 7 14:8:0 415 506 normal ld valid N --- ---
61 0 7 10:8:0 344 507 normal ld valid N --- ---
62 0 7 15:7:0 500 507 normal ld valid N --- ---
63 0 7 8:9:0 364 504 logging ld valid N --- ---
64 0 8 9:7:0 446 500 normal ld valid N --- ---
65 0 8 12:7:0 404 500 normal ld valid N --- ---
So I run the checkld command:
checkld -y -progress -recover 364:504 B3-C7000-VM.63.usr.3
Performing a kernel level consistency check, will try to fix inconsistencies
ld B3-C7000-VM.63.usr.3 has 9 rsets, checked 7, inconsistent 0
0 out of 1 lds ( 7 out of 9 rsets) have been checked, will check the ldck progress in 5 seconds ...
this command has run for 3 days, the current output is:
ld B3-C7000-VM.63.usr.3 has 9 rsets, checked 8, inconsistent 0
ld B3-C7000-VM.63.usr.3 has 9 rsets, checked 8, inconsistent 0
ld B3-C7000-VM.63.usr.3 has 9 rsets, checked 8, inconsistent 0
ld B3-C7000-VM.63.usr.3 has 9 rsets, checked 8, inconsistent 0
How time flies~~~
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-08-2020 04:50 AM
тАО10-08-2020 04:50 AM
Re: Questions about checkld recover LD
Hi Louis,
When a connection is lost to a physical disk or a physical disk fails, all future writes to the disk are automatically written to a logging LD until the physical disk comes back online, or until the time limit for logging is reached. Logging disk space is allocated when the system is set up. If the time limit for logging is reached, or if the logging LD becomes full, the relocation of chunklets on the physical disk to free chunklets designated as spares starts automatically.
So, this is not an issue to be concerned much. When the system goes on writing data and all the chunklets in the 'logging' LD are relocated to different LD, logging state will recover. As the LD size is bigger, it logging state may persist for an extended period.
Regards,
Srinivas
I am an HPE Employee