- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- ERROR E00020101
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
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
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
11-30-2011 09:18 AM
11-30-2011 09:18 AM
ERROR E00020101
I have this error on my lefthand (at the end of the message)
When i look at the date of the alarm, it correspond at the date that we made the update to the version 9.5 (yesterday)
All the lun are full lun
I will not create new lun until i will buy new nodes
I didn't use snapshot
I will not made new update until i will buy new nodes
I didn't have the alarm before
My question is:
Is it a problem for the next months for the performance, or was it just because between the update it need more space ?
thanks nicolas
The cluster 'CL_OCA' is becoming full. The cluster 'CL_OCA' space utilization is at 97.06% of capacity. This utilization value exceeds 95.00%. As the cluster approaches being full, scheduled snapshot or remote snapshot creation may fail due to a lack of space, application writes may fail on thinly provisioned volumes when the cluster is full, and other tasks that require cluster space may be impacted. Some actions to reduce capacity utilization on the SAN are to delete volumes and snapshots, reduce snapshot retention, add nodes to the storage cluster, use thin provisioning, switch large volumes from Network RAID 10 to Network RAID 5, move volumes to other clusters, etc.