Rollback RX vs TRIM - revisited

Very good to know, thanks. I look forward to hearing what HDS has to say on the issue(s).

 

Another week gone by,,,,I will be bumping this thread on a weekly basis so its not forgotten about.

 

Thought I'd give everyone a small update.

The team that's testing this SSD Trim setup by Froggie is currently very pre-occupied with Jira and Drive Cloner's Version 6. So when they have time, they are testing Froggies setup. So if we haven't responded in a while it's simply because we have other projects going on.

Our team did an some initial tests with Froggie's setup, and those initial tests show SSD trim is working. It's still ongoing, but I figured I'd let you all know where we're at.

Cheers,

 

From the FWIW Dept...

There are "tentative" plans afoot for HDS and myself to get together this coming week (Team Viewer <video> and Skype <audio>) so that I may walk them through my script/explanation and demonstrate why TRIM does not work with Rollback RX. If that comes off, I'll be reporting back here as to the results... PASS or FAIL

 

Yes. We're all trying to be on the same page, and while we assume we are, sometimes we need to communicate in a conversational sense, so I'm hoping that regardless of the outcome, both Froggie and Horizon Data Sys at least has the definitive answer.

Cheers,

 

That sounds promising,,,,, looking forward to hearing the outcome.

 

My non-TRIM demonstration for HDS is tentatively scheduled for Thursday, May 28th, at 10:30am PDT.

Wish both HDS and me luck with this one...

 

Thank you for informing us @TheRollbackFrog

Good luck on this one

 

Hi Froggie,

could you please explain why you must perform a live demonstration for them?
Trim either works or doesn't, and they should know the answer without the need of live demonstration. Unless they gave you an answer like "we cannot replicate the issue" a live demonstration is not necessary.

By the way, if the above is true, I would be far more interested to an opposite live demonstration, HDS employees proving that RollbackRX Trims the ssd on a system of their choice...

Panagiotis

 

Greetings, P...

That's basically what's being said to date... "Preliminarily my observations cannot be reproduced."

I have this inkling that TRIM to HDS may not mean what TRIM does to the rest of the SSD world... I'll sure know tomorrow. Either that or the "Company" doesn't know what the "Developers" know and that's why they keep saying all is well with TRIM. I don't know where the problem lies, but it will be definitively answered tomorrow and I will be happy to pass on what "we" learn.

Well... they say it works and based on that statement they feel they have nothing to prove. All of us will be on the same system at the same time... it should be fun!

 

Yup.

 

Thought it would be like that.
The problem lies to the fact that their policy is to deny any and all problems of their products.
ps. An advise: you should record the live session (their perception of reality seems to be very different from the rest of the world;... I would love to know what they are smoking...)

Panagiotis

 

The demonstration has been cancelled due to HDS Senior Tech health issues... will update later.

 

The demonstration has been rescheduled for Monday, 01June2015, at 10:30PDT... I'll keep everyone posted.

 

Rollback and TRIM... not so perfect together.

Just finished a remote demonstration for Horizon DataSys Senior Tech Support showing, unequivocly, that TRIM *DOES NOT FUNCTION* on a Rollback protected System partition (most likely any protected partition) located on an SSD. Both of us agreed that TRIM did not function correctly during the demonstration.

HDS will go back and reproduce the "anomaly" on one of their test systems and following that, bring it up with the Rollback developer(s) directly. Hopefully the Rollback development team can isolate and repair this anomaly as it's most likely been in place since the original introduction of SSD and TRIM support on July 18, 2011 in v9.1... and that's not a good thing for SSD-based Rollback users.

If I hear anything more from HDS on this situation, I"ll be happy to pass it along.

 

Just to clarify 1-2 things.
An "Anomaly" as HDS name it or a "Bug" more widely used in computer language

http://en.wikipedia.org/wiki/Software_bug#Etymology
This is neither an anomaly (as they describe it) nor a bug as the rest of the world names it. To have a bug there must be a code that should perform a certain action, that code misbehaves and does not get executed or performs another action.
But Rollback RX never had this function/code (send trim commands to the disk), so what is the anomaly/bug they are talking about?
Anomaly/bug for a non-existed action/feature, is not an anomaly but the normal behaviour.

They knew it, from at least February 2012, and they chose instead of fixing it (adding trim execution from their subsystem), to deny it, to virtualise the sparce file creation for preventing the various trim tools to work so that people would not complain and to give crap explanations about "colorful" sector allocations... http://community.horizondatasys.com...-ssd-trim-and-disk-defraggers-support#post997

Panagiotis

 

Congrads Froggie, well done. Now we wait to see how HDS will handle this going forward.

 

Thank for the info.

All these info, WOW, just WOW. Such a genius explanation from HDS.

 

If you ask HDS whether RBRX supports TRIM, they will say yes. And legally and by all interpretations of the statement that is correct.

The degree or level of support is an entirely different thing. In this context "support" can mean anything. From full implementation and interaction all the way down to disabling a feature or simply reporting on it. And the issue has been avoided since RBRX came out. We tested this years ago.

 

Well... it's been a month so I felt that a response to this issue was needed. That response has been posted in the GENERAL Rollback RX thread started recently

I would suggest to the moderators that this particular Rollback RX thread may be considered for closing as any further discussion on this issue will most likely occur in the general Thread mentioned above.