- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- MSA2000 vdisk mapping
Disk Enclosures
1748139
Members
3742
Online
108758
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
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
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
тАО11-17-2008 11:59 PM
тАО11-17-2008 11:59 PM
MSA2000 vdisk mapping
Hi, all.
Does anyone have any information about the following my situation?
I got an MSA2000, and tried to build a vdisk and map it to a windows OS.
I made 1073MB vdisk with MSA, and got 1GB new drive on the Windows OS.
After that, I configured a 536500byte vdisk on MSA to get new 500MB drive. Yet, the OS showed just only 499.65 MB.
Why such a kind of the capacity difference between MSA and Windows does occur?
How can I get a JUST 500MB disk drive on the OS?
Also, i'd like to know how many bytes are needed to configure other vdisk size, such as 2GB, 3GB, 4GB, 5GB,, etc.
Thanks.
Ashliee
Does anyone have any information about the following my situation?
I got an MSA2000, and tried to build a vdisk and map it to a windows OS.
I made 1073MB vdisk with MSA, and got 1GB new drive on the Windows OS.
After that, I configured a 536500byte vdisk on MSA to get new 500MB drive. Yet, the OS showed just only 499.65 MB.
Why such a kind of the capacity difference between MSA and Windows does occur?
How can I get a JUST 500MB disk drive on the OS?
Also, i'd like to know how many bytes are needed to configure other vdisk size, such as 2GB, 3GB, 4GB, 5GB,, etc.
Thanks.
Ashliee
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2008 11:50 PM
тАО11-18-2008 11:50 PM
Re: MSA2000 vdisk mapping
Hello Ashliee,
it looks like you are fighting with the "Hardware GigaBytes" vs. "Software GigaBytes" problem.
Some software takes the number of logical blocks of a volume, multiplies it by 512 Bytes/Block and then divides it by (1000*1000*1000) to get the number of "Hardware GigaBytes". This value is usually printed on the disk drive hardware.
Other program code divides by (1024*1024*1024) and gets the number of "Software GigaBytes". The value looks a bit less, but it is just a different number system and not the cause for a law suit ;-)
It looks like this is the case with the MSA vs. Windows:
536.5/1.024/1.024/1.024 = 499.65456
Maybe you will never get a 'nice round 500 MBytes' on Windows, because you would have to create a volume of 536.87091199999998 MBytes which the MSA might not allow.
it looks like you are fighting with the "Hardware GigaBytes" vs. "Software GigaBytes" problem.
Some software takes the number of logical blocks of a volume, multiplies it by 512 Bytes/Block and then divides it by (1000*1000*1000) to get the number of "Hardware GigaBytes". This value is usually printed on the disk drive hardware.
Other program code divides by (1024*1024*1024) and gets the number of "Software GigaBytes". The value looks a bit less, but it is just a different number system and not the cause for a law suit ;-)
It looks like this is the case with the MSA vs. Windows:
536.5/1.024/1.024/1.024 = 499.65456
Maybe you will never get a 'nice round 500 MBytes' on Windows, because you would have to create a volume of 536.87091199999998 MBytes which the MSA might not allow.
.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-19-2008 07:43 PM
тАО11-19-2008 07:43 PM
Re: MSA2000 vdisk mapping
Hi, Uwe.
Thanks to reply to my post.
I did never consider the differences at all.
But I'll try 536.87091199999998 MB on MSA.
Thanks to reply to my post.
I did never consider the differences at all.
But I'll try 536.87091199999998 MB on MSA.
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