GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- SAN/iQ 9 Problems reporting consumed space
StoreVirtual Storage
1854671
Members
18578
Online
104102
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
12-28-2010 02:47 AM
12-28-2010 02:47 AM
SAN/iQ 9 Problems reporting consumed space
Our customer has HP Lefthand P4300 G2 nodes with SAN/IQ 9, some nodes were purchased with this version, other were upgraded from 8.5. Now all the nodes have the latest versions of firmware. The host servers are running VMWare ESXi 4.1.
The biggest problem is when the CMC reports consumend space for volumes, for example, we have a volume 2 way replicated, thin provisioned max dimension 640 GB, consumed space: 1 TB (this is almost true because the volume has around 480 GB of data, this is what ESXi shows). When the customer changed the the volume from thin provision to thick provision, the cosumend space started to show 2,2 TB witch is terribly wrong because the volume is 2-way replicated.
This situation didn't occour just to this volume, first the customer dicovered this when he tried to make a large volume of 1,6 TB from thin to thick and the CMC told him that it doesn't have enough space, witch it was not true.
The customer uses 3 nodes clusters and the volumes that had this issues also are remotely replicated using scheduled remote snapshot. The snapshot isn't larger then max, 5 GB, this can be seen from the time it takes to finish the transfer to the remote location.
The biggest problem is when the CMC reports consumend space for volumes, for example, we have a volume 2 way replicated, thin provisioned max dimension 640 GB, consumed space: 1 TB (this is almost true because the volume has around 480 GB of data, this is what ESXi shows). When the customer changed the the volume from thin provision to thick provision, the cosumend space started to show 2,2 TB witch is terribly wrong because the volume is 2-way replicated.
This situation didn't occour just to this volume, first the customer dicovered this when he tried to make a large volume of 1,6 TB from thin to thick and the CMC told him that it doesn't have enough space, witch it was not true.
The customer uses 3 nodes clusters and the volumes that had this issues also are remotely replicated using scheduled remote snapshot. The snapshot isn't larger then max, 5 GB, this can be seen from the time it takes to finish the transfer to the remote location.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP