01-28-2013 09:35 AM - last edited on 11-20-2013 05:25 PM by Maiko-I
I wanted to ask if there are any News on TRIM/DISCARD functionality on P4500 ... We are using several thin provisioned Partitions - and they are growing every day because of the lack of trim/discard ...
Hope this Feature will be implemented soon? (As most other SAN already can do it ...)
P.S. This thread has been moved from HP 3PAR StoreServ Storage to HP StoreVirtual Storage / LeftHand. - Hp Forum Moderator
02-01-2013 01:30 AM
I hope they don't neglect P4000 Features in favor of the 3PAR ... wouldn't be the first time that some features would be retained in favor of bigger Machines ... Hope I'm wrong with this thought ...
02-01-2013 01:45 AM
I don't think that HP will keep this for 3PAR only since P4000 is also a major platform for HP...
My opinion (no I do not work for HP) is that it will be implemented in 10.5... 10.0 was mote a hardware refresh than a software one, I assume that 10.5 will be also a bigger software update, just like it was the case with 9.5...
If my post was useful, clik on my KUDOS! "White Star" !
My blog: http://blog.bitcon.be
02-04-2013 12:15 AM
3Par strips the "0" in the asic and don't even write the "0" to disk.
Lefthand must implement this in a other way (writing - finding - removing) as the architecture does not have a asic.
Having said that I suspect this is functionallity HP i looking into and it is obviously harder to do this in a "scale-out" storage approach compared to legacy two-controller systems. Hopefully it can be implememented without to much of a performance impact. Might also be a "G3 only solution"? (I don't know)
(I'm not working for HP)
02-04-2013 01:44 AM
I've heard rumours that v10.5 is going live with new StoreVirtual (4530 and 4730) models in two weeks (on February 19th). Don't know anything exact about new features (SMI-S might be supported, otherwise why new OS version number?). Regarding TRIM/DISCARD/T10 SCSI UNMAP etc., that is for sure not in this release.
02-04-2013 02:49 AM
02-04-2013 04:19 AM
This information would generally not be avaliable without current a NDA. (Closer to product launch more and more people will know something)
Generally HP (and others) talks very little about futureware. I guess this is related regulations by the stock exchange.
Doesn't mean that I don't want to know, but I can see their side of this information flow also.
02-04-2013 05:08 AM
Regarding information disclosure and stocks, etc. - that is probably related. Or not, only HP might tell.
But some NDA or 'partner only' presentations do get leaked on internet and mighty google indexes them :) Try search for StoreVirtual part numbers 4530 and 4730, some info is already present
07-11-2013 06:50 AM
oh that would be such a relief. I can't wait, but I hope they include SMI-S support and some integration with the storage services of windows 2012, but that might just be a dream.
03-24-2014 05:34 AM
On our Servers we habe 2TB used Space (4,6TB assigned; 2TB used) - which eats up over 9TB on our LH Storage. So our P4500 is nearly filled up by 100% ...
Only thing we can do is move the Partitions to newly created Volumes - but they soon will fill up again ...
So if there is no discard/trim support in the very near future it seems we need to drop HP SAN and look for an alternative which supports it ... :-/
I don't like that - as we were always very satisfied with HP - but I don't see another solution at the moment ...
03-24-2014 06:19 AM
Hope you get that to the right ears over there. I'm too small of a fish to make any difference to them when I say that. In the meantime, what is your actual usage? Can you move your high churn data to isolated smaller LUNs and your lower movement stuff to other drives? that way you can limit the amount of thin LUNs that actually expand out to their full size. That was how I managed to get a bit of control on our thin provisioning LUN expansion rates. I also have to monitor it just in case something grows too quickly so I can move everything off that LUN and onto another thin LUN while I still have the space... its a PITA, but it keeps our allocation where we want it.
03-24-2014 06:55 AM
I just had a Phone-Call from HP Support (DAMIAN IVANOV) because of a Support Request on this issue (Case ID: #4647850281) - and HP Support (DAMIAN IVANOV) told me clearly that Lefthand Engeneering !!! IS CURRENTLY NOT !!! working on DISCARD funtionality nor will it come in the foreseeable future ... !!!
Support Case answer:
*** PHONE LOG 3/24/2014 (M/D/Y) 2:23 PM CET-1CEST AT [UTC +1:00] WIDEN_DAMIAN_IVANOV Action Type: Outgoing call
Talked to the customer. There is no official info on this if he got that info from 3rd party / sales team he should contact them.
He suggested to move to 3PAR Storage ...
Seems like we're left out in the rain!!
03-24-2014 08:06 AM
that sucks x2. Not sure the workaround there. what exactly are you selling here? do they see the LUN or are they just getting a VM w/ virtual disks? What hypervisor? I"m using hyper-v and what I did was move any vhd files which caused thin volume expansion to a set of LUNs where I assume they were expaned to 100% capacity for thin provisioning. Then I moved the other disks to LUNs where I assumed I wanted to keep them compacted and any time their compaction rate goes down too far, I create a new LUN, migrate the vhd files to that. Then when I have the old expanded LUN empty, I shrink it to 1GB and then re-expand it to make it "thin" again. As long as I can keep enough space available for one extra LUN, I don't have an issue... this isn't idea, but I viewed it as a nice temporary solution. This this isn't temporary as your support response seems to suggest, I too will be migrating to a non-HP solution next year. Its a shame since this product used to be so good and now it sounds like its just getting left behind.
03-24-2014 09:33 AM
I had the chance to speak with Brad Katz (HP WorldWide Product Manager StoreVirtual) ... sounds way better than the Support Rep. statement ...
The support person was incorrect if they said no one is working on this. The UNMAP feature is being actively worked as a high priority by our development team and we expect to deliver this feature to our customers this year.
Looking forward for the UNMAP Feature ... ;-)