- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA3000 with mixed drive types
Disk Enclosures
1754265
Members
3104
Online
108813
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
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
04-06-2005 03:51 AM
04-06-2005 03:51 AM
EVA3000 with mixed drive types
Hello,
Case: EVA3000 historical configuration with a number of 72 GB disks and a number of 300GB add-on disks in the default DG.
With Command View I can check the default DG.
I have a raw capacity for this DG of appr. 1900GB and a total storage space of ~1250GB (net available). The storage space used is appr. 550GB, so actual available space is ~700GB.
The disk group properties say:
Occupancy: 550GB, failure prot. single
This is clear and looks OK for sparing level setting etc.
Strange thing is the following:
In the diskgroup properties there is also:
Total capacity: 1241GB
available:
Vraid0 362GB
Vraid1 181GB
Vraid5 182GB
When creating a new vdisk I cannot go greater than this 362GB for a Vraid0 disk while ~700GB is available.
Can anyone explain this? Is this because there is a mix of two types of disks in this DG?
Thanks,
Philip
Case: EVA3000 historical configuration with a number of 72 GB disks and a number of 300GB add-on disks in the default DG.
With Command View I can check the default DG.
I have a raw capacity for this DG of appr. 1900GB and a total storage space of ~1250GB (net available). The storage space used is appr. 550GB, so actual available space is ~700GB.
The disk group properties say:
Occupancy: 550GB, failure prot. single
This is clear and looks OK for sparing level setting etc.
Strange thing is the following:
In the diskgroup properties there is also:
Total capacity: 1241GB
available:
Vraid0 362GB
Vraid1 181GB
Vraid5 182GB
When creating a new vdisk I cannot go greater than this 362GB for a Vraid0 disk while ~700GB is available.
Can anyone explain this? Is this because there is a mix of two types of disks in this DG?
Thanks,
Philip
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2005 01:12 PM
04-06-2005 01:12 PM
Re: EVA3000 with mixed drive types
You may want to create an official support case for this. The numbers sound a little out of whack. The system is not still actively rebalancing/leveling (or some such)? Gave it enough time to settle?
Just today someone posted an Eva best practices document in the hpux forum: http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=850958
> Is this because there is a mix of two types of disks in this DG?
The document attached to the above suggest that the Eva nicely incorporates all the space. I quote:
"The EVA will attempt to ensure that the amount on each physical disk drive is proportional to that driveâ s contribution to the overall capacity. This means that larger drives will have more data on them than smaller drives. As an example, a 72 GB disk will have twice as much user data on it as a 36 GB drive. In a random access type of application, this implies that the larger drives will have twice as much I/O as the smaller drives, resulting in an I/O load imbalance at the disk drive level."
Hope this helps a little....
Hei
Just today someone posted an Eva best practices document in the hpux forum: http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=850958
> Is this because there is a mix of two types of disks in this DG?
The document attached to the above suggest that the Eva nicely incorporates all the space. I quote:
"The EVA will attempt to ensure that the amount on each physical disk drive is proportional to that driveâ s contribution to the overall capacity. This means that larger drives will have more data on them than smaller drives. As an example, a 72 GB disk will have twice as much user data on it as a 36 GB drive. In a random access type of application, this implies that the larger drives will have twice as much I/O as the smaller drives, resulting in an I/O load imbalance at the disk drive level."
Hope this helps a little....
Hei
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP