- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Defrag CSV on 3PAR (volume alignment is invalid)
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
04-04-2016 03:39 PM
04-04-2016 03:39 PM
Defrag CSV on 3PAR (volume alignment is invalid)
I was trying to check the fragmentation level on a CSV we have setup for our Hyper-V cluster. This is running on our 3PAR 7200 and it returns:
"The slab consoluidation / trim operation cannot be performed because the volume alignment is invalid (0x89000029)"
I've seen this post on Microsoft about some NetApp storage and 3PAR stating:
Reference this:
msdn.microsoft.com/…/hh449432(v=vs.85).aspx
and tell them the violation is that OptimalUnmapGranularity or UnmapGranularityAlignment aren’t multiples of cluster size. If you know the slab size, you can choose a cluster size that meets these requirements.
Is this an issue I need to open a case with HP about? I'm running Server 2012 R2 with the latest updates.