The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
Installed v8.0,6345, created a test LUN of 500GB , I tried 1024GB but still got that message.fbifido wrote:Hi,
just installed v8.0.6312(beta-3)
Tried to create a 1024GB thin LUN, but failed with error message, see pic below.
http://i44.tinypic.com/t69w93.png (full image)
http://oi44.tinypic.com/t69w93.jpg (RAW image)
I have 12GB RAM, about 2G is been used.
I have 4TB SAS, about 2TB free.
I tried creating a 10GB LUN, I did not get that error.
I tried 100GB LUN, did not get that error.
tried 500GB LUN, no error
tried 900GB LUN, no error
Tried 1024GB LUN, error
Tried 1TB LUN, error.
just saw this info from a post and tried it.Better use it AS IS (LSFS but no deduplication) and use flash as a flash cache. More IOPS.
Are you talking about v6 to v8b3 update? v6 to v8b3 must work fine.2. The problem of LUN disappearance from esxi 5.5 storage when I update iSCSI san and restart esxi.
Thanks! We reproduced the problem. Working on the fix. I believe the new build will be available in 1-2 days.sbozhko wrote:I got this error on two different systems:
1. Operating System Microsoft Windows Server 2012 R2 Standard 6.3.9600.16452 (Win8.1 RTM)
CPU Type 2x OctalCore Intel Xeon E5-2680, 1200 MHz (12 x 100)
Motherboard Name Dell PowerEdge R720xd
System Memory 131026 MB (DDR3 SDRAM)
Storage Controller PERC H710P Mini
Disk Drive DELL PERC H710P SCSI Disk Device (185 GB) (RAID 10)
Disk Drive DELL PERC H710P SCSI Disk Device (19268 GB) (RAID 10)
2. Operating System Microsoft Windows Server 2012 R2 Standard 6.3.9600.16452 (Win8.1 RTM)
CPU Type 2x QuadCore Intel Xeon E5335, 2000 MHz (6 x 333)
Motherboard Name Supermicro X7DB8 (3 PCI-E x8, 3 PCI-X, 1 SEPC, 8 FB-DIMM, Video, Dual Gigabit LAN, SCSI)
System Memory 24576 MB (DDR2-667 Fully Buffered ECC DDR2 SDRAM)
Storage Controller Adaptec RAID 6805/6805Q
Disk Drive Adaptec Array SCSI Disk Device (278 GB) (RAID 10)
Disk Drive Adaptec Array SCSI Disk Device (2399 GB) (RAID 10)
Disk Drive Adaptec Array SCSI Disk Device (2796 GB) (RAID 5)
it was v8b3(8.0.6312) to v8b3(8.0.6345)Bohdan (staff) wrote:v8b1, v8b2 update to v8b3 may cause the LUN disappearance.2. The problem of LUN disappearance from esxi 5.5 storage when I update iSCSI san and restart esxi.
Please make sure this is not v8beta1 (or v8beta2) to v8beta3 update.
Sorry but, don't scare people like that.Vitalii (staff) wrote:When the new LSFS device is created it does not use all needed memory. Memory usage grows as device is filled with data.
Maximum size restriction is based on the assumption, that there should be enough memory to support 100% full device. Until that, it does not use additional memory, so it is still available for the system.
That is why, you are able to create multiple devices of smaller size, but are not able to create single large device.
Vitalii
Please re-download the beta build. It should solve the problem.sbozhko wrote:I got this error on two different systems:
Yesfbifido wrote: I create a LSFS LUN, it checks the free memory I have and then calculate what is the max LSFS I can create and if what I want is greater it lets me know, and make a recommendation, now this suggestion is base that if this LUN became full then all the memory in my server will be fully use (yes/No)?
Yesfbifido wrote: What if I had created 2 LUN, does that means the if one of them is at 100% the system will run out of memeory? (Please don't tell me this is like that FreeBSD dedup problem)
It is not a requirement. It is warning. Due to changes/fixes related to vendor/product, serialId and eui-64 identifier there is possibility of datastore disappearance and and necessity to manually re-add them.turkina wrote:Is it still a requirement to only update to the latest beta build from v6 and that updating to the latest beta build from a previous beta build could fail?
What if we're not using LSFS and only image files? Then is an upgrade from beta2 to beta3 safer?Bohdan (staff) wrote:It is not a requirement. It is warning. Due to changes/fixes related to vendor/product, serialId and eui-64 identifier there is possibility of datastore disappearance and and necessity to manually re-add them.turkina wrote:Is it still a requirement to only update to the latest beta build from v6 and that updating to the latest beta build from a previous beta build could fail?
v6 to v8b3 (6345 or later) should work fine for all device types.
LSFS device update should work fine in v8b3 (6383 or later).
Thanks! With the new build I have successfully created LSFS volume on a large partition!Bohdan (staff) wrote:Please re-download the beta build. It should solve the problem.sbozhko wrote:I got this error on two different systems:
http://starwindsoftware.com/tmplink/StarWindBeta.exe