Flashes (Alerts)
Abstract
Track Space Efficient (TSE) repositories greater than 50TB (>51200 GB) are not supported. If TSE repositories greater than 19TB (>19456 GB) are used - they are exposed to corruption of the data contained in the repository that can result in a loss of access to the DS8100/DS8300/DS8700/DS8800/DS8870.
Content
The problem is caused by an internal condition that results in overwriting a structure in memory if the repository size is greater than 19 TB. The overwrite will happen during cluster Quiesce/Resume and cluster Failover/Failback. The corruption will affect customers differently, from no impact to as severe as corrupting repository data and causing loss of access.
This problem affects both CKD and FB type of storage repositories. TSE feature was introduced in R3.0 GA bundle (63.0.102.0), and the repository restriction affects all machine types DS8100/DS8300/DS8700/DS8800/DS8870
Mitigation:
Repositories are 19TB (repcap_size 19456 GB) and smaller there is no action is required
Repositories larger than 19TB (repcap_size > 19456 GB) up to 50 TB (repcap_size > 51200 GB) need to
-> delete these repositories
-> upgrade to a bundle with the fix installed. (see Resolution table below)
Repositories larger then 50 TB (repcap_size > 51200 GB) are not supported in any µ-code level and need to be deleted
Resolution:
A fix is available for the following affected models DS8100/DS8300/DS8700/DS8800/DS8870.
Product | Fix Bundle |
DS8100/DS8300 | 64.36.99.0 |
DS8700 | 76.31.105.0 |
DS8800 | 86.31.123.0 |
DS8870 | 87.50.114.0 |
Customers with repositories larger than 19TB (repcap_size > 19456 GB) should delete these extra repositories. Do not create any repositories greater than 19TB (repcap_size > 19456 GB) until code containing the fix has been loaded on both DS8000 successfully.
Warning: If the warnings contained in this notification are not followed this can result in corrupting repository data / fencing the repository and loosing access to all storage.
1) repository sizes greater than 19 TB and up to 50 TB are only supported when the fix mentioned in the table above is installed
2) DS8000 does not support repository sizes bigger then 50 TB in any micro code level.
Commands:
How to identify if the TSE repository is larger than 19TB
A TSE repository should be removed if the storage it has allocated is larger than 19TB. If the TSE repository storage is over 19TB, the dscli command lssestg will return a repcap value that is larger than 19456.
If the repcap value returned is larger than 19TB (repcap > 19456), the repository storage will need to be deleted and reallocated.
The following example displays a TSE repository with 20TB allocated in extent pool P0.
dscli> lssestg -l
Date/Time: February 19, 2014 11:04:02 PM MST IBM DSCLI Version: 7.7.10.291 DS: IBM.2107-75BLM31
extpool stgtype datastate configstate repcapstatus repcap(GiB/Mod1) vircap repcapalloc vircapalloc
===================================================================================================
P0 fb Normal Normal below 20480.0 25000.0 0.0 640.0
dscli>
In this example, the repository belongs to extent pool P0. This repository must be deleted because the repcap value is 20480, which is larger than 19456.
The dscli command lsfbvol or lsckdvol can be used to find volumes associated with a large repository:
For FB : lsfbvol -sam tse -extpool P0 where P0 is extent pool that contains the >19 TB repository
For CKD lsckdvol -sam tse -extpool P0 where P0 is extent pool that contains the >19 TB repository
These TSE volumes must be removed before removing the TSE repository storage
In the following example, we are looking for TSE volumes in extent pool P0. These are the TSE volumes that belong to the TSE repository storage that should be deleted.
The volume IDs of the volumes that should be deleted are in bold.
dscli> lsfbvol -sam tse -extpool P0
Date/Time: February 20, 2014 9:28:33 PM MST IBM DSCLI Version: 7.7.10.291 DS: IBM.2107-75BLM31
Name ID accstate datastate configstate deviceMTM datatype extpool cap (2^30B) cap (10^9B) cap (blocks)
========================================================================================================
- 0000 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 0001 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 0002 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 0003 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 0004 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 0005 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 0006 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 0007 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 0008 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 0009 Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 000A Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 000B Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 000C Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 000D Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 000E Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
- 000F Online Normal Normal 2107-900 FB 512 P0 20.0 - 41943040
dscli>
To remove TSE repository storage, you must first remove all the TSE volumes in the repository. After removing the TSE volumes, the repository storage can be deleted.
Using the dscli command of rmfbvol or rmckdvol, depending on the storage type.
From the previous example, we found TSE volume ids 0000-000f that should be deleted..
dscli> rmfbvol 0000-000f
Date/Time: February 20, 2014 9:33:25 PM MST IBM DSCLI Version: 7.7.10.291 DS: IBM.2107-75BLM31
CMUC00027W rmfbvol: Are you sure you want to delete FB volume 0000-000f? [y/n]: y
CMUC00028I rmfbvol: FB volume 0000 successfully deleted.
CMUC00028I rmfbvol: FB volume 0001 successfully deleted.
CMUC00028I rmfbvol: FB volume 0002 successfully deleted.
CMUC00028I rmfbvol: FB volume 0003 successfully deleted.
CMUC00028I rmfbvol: FB volume 0004 successfully deleted.
CMUC00028I rmfbvol: FB volume 0005 successfully deleted.
CMUC00028I rmfbvol: FB volume 0006 successfully deleted.
CMUC00028I rmfbvol: FB volume 0007 successfully deleted.
CMUC00028I rmfbvol: FB volume 0008 successfully deleted.
CMUC00028I rmfbvol: FB volume 0009 successfully deleted.
CMUC00028I rmfbvol: FB volume 000A successfully deleted.
CMUC00028I rmfbvol: FB volume 000B successfully deleted.
CMUC00028I rmfbvol: FB volume 000C successfully deleted.
CMUC00028I rmfbvol: FB volume 000D successfully deleted.
CMUC00028I rmfbvol: FB volume 000E successfully deleted.
CMUC00028I rmfbvol: FB volume 000F successfully deleted.
dscli>
After all TSE volumes in the repository have been deleted, the repository may be deleted.
Deleting the repository will use chsestg command. This command will remove the TSE repository storage without removing the ESE storage.
By making the repcap = 0, this will remove the TSE repository. The virtual capacity will not be modified.
Here's an example:
Step 1 -- Query the Space Efficient Storage
dscli> lssestg -l
Date/Time: February 20, 2014 9:37:31 PM MST IBM DSCLI Version: 7.7.10.291 DS: IBM.2107-75BLM31
extpool stgtype datastate configstate repcapstatus repcap(GiB/Mod1) vircap repcapalloc vircapalloc
===================================================================================================
P0 fb Normal Normal below 20480.0 25000.0 0.0 320.0
Step 2 -- Remove the TSE storage:
dscli> chsestg -repcap 0 P0
Date/Time: February 20, 2014 9:37:44 PM MST IBM DSCLI Version: 7.7.10.291 DS: IBM.2107-75BLM31
CMUC00414W chsestg: Are you sure that you want to remove the physical repository for space-efficient storage from extent pool P0? [y/n]: y
CMUC00343I chsestg: The space-efficient storage for the extent pool P0 has been modified successfully.
Step 3 -- Query the Space Efficient Storage - verify that repcap = 0
dscli> lssestg -l
Date/Time: February 20, 2014 9:37:59 PM MST IBM DSCLI Version: 7.7.10.291 DS: IBM.2107-75BLM31
extpool stgtype datastate configstate repcapstatus repcap(GiB/Mod1) vircap repcapalloc vircapalloc
===================================================================================================
P0 fb Normal Normal - 0.0 25000.0 - 320.0
dscli>
The TSE repository must be created again before the TSE volumes can be created. First check if the space-efficient storage currently exist.
By using the chsestg command the TSE storage can be allocated. When reallocating the storage, be sure that repcap is not greater than 19456.
In the following example, TSE storage of 19TB will be allocated by setting the repcap = 19456. The query shows the space that was allocated.
dscli> chsestg -repcap 19456 P0
Date/Time: February 20, 2014 9:48:49 PM MST IBM DSCLI Version: 7.7.10.291 DS: IBM.2107-75BLM31
CMUC00343I chsestg: The space-efficient storage for the extent pool P0 has been modified successfully.
dscli>
dscli> lssestg -l
Date/Time: February 20, 2014 9:50:36 PM MST IBM DSCLI Version: 7.7.10.291 DS: IBM.2107-75BLM31
extpool stgtype datastate configstate repcapstatus repcap(GiB/Mod1) vircap repcapalloc vircapalloc
===================================================================================================
P0 fb Normal Normal below 19456.0 25000.0 0.0 320.0
dscli>
To create the volumes, use mkfbvol or mkckdvol depending on storage type.
In the following example, the mkfbvol command will be re-creating the 16 volumes that were deleted earlier
dscli> mkfbvol -sam tse -cap 20 -extpool P0 0000-000f
Date/Time: February 20, 2014 9:57:22 PM MST IBM DSCLI Version: 7.7.10.291 DS: IBM.2107-75BLM31
CMUC00025I mkfbvol: FB volume 0000 successfully created.
CMUC00025I mkfbvol: FB volume 0001 successfully created.
CMUC00025I mkfbvol: FB volume 0002 successfully created.
CMUC00025I mkfbvol: FB volume 0003 successfully created.
CMUC00025I mkfbvol: FB volume 0004 successfully created.
CMUC00025I mkfbvol: FB volume 0005 successfully created.
CMUC00025I mkfbvol: FB volume 0006 successfully created.
CMUC00025I mkfbvol: FB volume 0007 successfully created.
CMUC00025I mkfbvol: FB volume 0008 successfully created.
CMUC00025I mkfbvol: FB volume 0009 successfully created.
CMUC00025I mkfbvol: FB volume 000A successfully created.
CMUC00025I mkfbvol: FB volume 000B successfully created.
CMUC00025I mkfbvol: FB volume 000C successfully created.
CMUC00025I mkfbvol: FB volume 000D successfully created.
CMUC00025I mkfbvol: FB volume 000E successfully created.
CMUC00025I mkfbvol: FB volume 000F successfully created.
First Published Date: 02/24/2014
[{"Product":{"code":"HW2B2","label":"Disk systems->DS8100"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"","label":"N\/A"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}},{"Product":{"code":"HW2C2","label":"Disk systems->DS8300"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"","label":"N\/A"}],"Version":"Version Independent","Edition":"N\/A","Line of Business":{"code":"","label":""}},{"Product":{"code":"STUVMB","label":"Disk systems->DS8700"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"N\/A","Line of Business":{"code":"LOB26","label":"Storage"}},{"Product":{"code":"STXN8P","label":"IBM DS8800"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"N\/A","Line of Business":{"code":"LOB26","label":"Storage"}},{"Product":{"code":"ST8NCA","label":"Disk systems->DS8870"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"","label":"N\/A"}],"Version":"Version Independent","Edition":"N\/A","Line of Business":{"code":"LOB26","label":"Storage"}}]
Was this topic helpful?
Document Information
Modified date:
25 September 2022
UID
ssg1S1004551