Jump to content
Division-M Community
Anthony

Drive Bender v2.7.0.0 released

Recommended Posts

Release v2.7.0.0 release (2017-08-31)
[ b ] Balancing and landing zone clearing can start at the same time causing the other to abort.
[ b ] When files are being balanced, certain conditions can cause this process to hang, resulting in timeout errors and/or file system hangs.
[ u ] "Non-pool used space" is now scanned as part of the file health system scan, and is no longer estimated.
[ u ] Improved file locking resulting in I/O speed improvements.
[ b ] Fixed a number of minor bugs related to worker thread tasks and queues.
[ u ] Windows Server Dashboard is now more Server 2016 aware.
[ b ] Fixed a number of minor bugs related to the Drive Bender Manager.

Download here

Share this post


Link to post
Share on other sites

Attempted install of 2.7.0.0 on my WHS2011 box. Install fails with unknown error and says it's rolling back! 2.6.0.0 installs fine.

Before install I uninstalled 2.6.0.0 and restarted. Then tried running by just double clicking and also right clicking and selecting Run as admin. Fails either way.

Share this post


Link to post
Share on other sites

I tried to upgrade a friend's PC (Windows 7) from v2.3.9 to v2.7 and it installed OK, but the MANAGER window never responded, so I couldn't get the pool back online.

 

I didn't have much time, so I uninstalled and installed v2.6 which worked straight away.

 

No v2.7, but at least an upgrade from v2.3.9 to v2.6 was achieved

 

Not sure if there are any leftover logs, but I can take a look later this week.

 

 

 

Share this post


Link to post
Share on other sites
On 04/09/2017 at 5:17 PM, CBers said:

Thanks Anthony.

 

Would still like more clarification on what "Non-pool used space" is emoji3.png

This is any file on a pooled drive outside of the pool. This is displayed in that DB Manager, however previous versions estimated this value based on what DB had used in the pool, and the size of the drive etc (the issue with this method is that DB calculates real file size values, but files use more space than the size of the files themselves... known as slack space). Anyway , we now physically check and audit these non-pool files to give an accurate figure.

20 hours ago, w3wilkes said:

Attempted install of 2.7.0.0 on my WHS2011 box. Install fails with unknown error and says it's rolling back! 2.6.0.0 installs fine.

Before install I uninstalled 2.6.0.0 and restarted. Then tried running by just double clicking and also right clicking and selecting Run as admin. Fails either way.

I'm looking into this now.

Share this post


Link to post
Share on other sites

Ok, this "rollback" issue is sorted, simply re-download the v2.7.0.0 installation and run again. The issue was a small bug in one of the installer dll's, however, it only impacted Server versions of Windows.

@CBer - Re-checked against Windows 7 and there was no issue. I suspect there may have been a driver upgrade problem, and a re-install may have sorted. Anyway, try the new installer and give me a shout if still no good.

Share this post


Link to post
Share on other sites



This is any file on a pooled drive outside of the pool. This is displayed in that DB Manager, however previous versions estimated this value based on what DB had used in the pool, and the size of the drive etc (the issue with this method is that DB calculates real file size values, but files use more space than the size of the files themselves... known as slack space). Anyway , we now physically check and audit these non-pool files to give an accurate figure.


I don't have any files on my drives outside of the pool, so I'm confused.

Share this post


Link to post
Share on other sites
13 hours ago, CBers said:

I don't have any files on my drives outside of the pool, so I'm confused.

 

 

For some users, there are files outside of the pool, and this value (see screenshots) has been there for a number of years. However, it can report an incorrect size, which has caused some support issues (other than being an interesting value, it means nothing else). Anyways... if there are files outside of the pool on the drive(s), this value now reports the size correctly :-)

non_pool_1.jpg

non_pool_2.jpg

Share this post


Link to post
Share on other sites

So if there are no files on a pooled drive outside of the pool, that value should always be zero?

 

Otherwise, there's a bug or an issue.

 

Under DB v2.6, it's telling me I have 5.6Gb of Non-pool space used.

 

3c3897e2f990fb6f0de9bbc2a8fa8ed6.jpg

 

 

I'll update to v2.7 and see if it disappears.

 

 

 

Share this post


Link to post
Share on other sites

 

2 hours ago, CBers said:
I'll update to v2.7 and see if it disappears.

OK, under DB v2.7, it's now zero (see attached).

BTW, installation of DB v2.7 went without a hitch under Windows 10.

Capture1143.jpg

Share this post


Link to post
Share on other sites

Just upgraded to v2.7.0 on WHS2011 and during install received an error regarding DriveBender.dll:

 

Unable to copy the core library file: C:\Program Files\Division-M\Drive Bender\lib\v5\DriveBender.dll to C:\Program Files\Division-M\Drive Bender\DriveBender.dll

 

The install completed and the drive pool has come up successfully so no problems there. However if I check the DLL version in the main program folder it's still v2.5.0.0.

 

Would a reinstall help or does this need the service stopping, new DLL manually copying and then registering please?

 

Share this post


Link to post
Share on other sites
Do you have the latest version of v2.7?

You could try uninstallling and reinstalling.


I do indeed have the latest version of 2.7 as I only downloaded it yesterday.

While I could uninstall and reinstall, as it essentially works at the moment thought I'd ask if there was a quick way to resolve.

Share this post


Link to post
Share on other sites

When you installed DB did you first in-install the prior version and reboot before you installed 2.7.0.0? I ask because this installed fine on my WHS2011 box. What version of drivebender.dll is in C:\Program Files\Division-M\Drive Bender\lib\v5, if it's the 2.7.0.0 version can you manually copy it?

Share this post


Link to post
Share on other sites
When you installed DB did you first in-install the prior version and reboot before you installed 2.7.0.0? I ask because this installed fine on my WHS2011 box. What version of drivebender.dll is in C:\Program Files\Division-M\Drive Bender\lib\v5, if it's the 2.7.0.0 version can you manually copy it?

Yep, was already running v2.6 before the upgrade. Given the DLL version in use is 2.5 I suspect that upgrade also didn't update the DLL.

The version in the C:\Program Files\Division-M\Drive Bender\lib\v5 folder is the 2.7.0.0 version. It should be possible to copy it to the program folder proper without the service running but I don't know if it needs registering or is simply a resource file.

I've logged a support call so I'll update this post when I hear back from them.

Share this post


Link to post
Share on other sites
On 11.9.2017 at 9:21 PM, JonnyManiac said:


Yep, was already running v2.6 before the upgrade. Given the DLL version in use is 2.5 I suspect that upgrade also didn't update the DLL.

The version in the C:\Program Files\Division-M\Drive Bender\lib\v5 folder is the 2.7.0.0 version. It should be possible to copy it to the program folder proper without the service running but I don't know if it needs registering or is simply a resource file.

I've logged a support call so I'll update this post when I hear back from them.

I ran into the same issue but frankly didn't give it another thought, as Drive Bender is working. However, your're right. The dll version in the programs folder is still the older one. So thanks for pointing this out! If you've got a solution it would be nice if you would share it... :)

Share this post


Link to post
Share on other sites
I ran into the same issue but frankly didn't give it another thought, as Drive Bender is working. However, your're right. The dll version in the programs folder is still the older one. So thanks for pointing this out! If you've got a solution it would be nice if you would share it... 

I've a call open at the moment so once I know anything I'll post it here. Although I'm sure if it's anything serious Anthony will post anyway. So far he has stated that this version of the DLL should work with DB 2.7 without any issues.

Share this post


Link to post
Share on other sites

To fix the DLL issue if it has not been updated:

- Stop any services that might be using the DriveBender volume such as backup software etc.
- Using the Services management console in Windows Stop the ‘Drive Bender Service’. You might be promoted to Stop other dependent services which will be listed, click Yes and let them cleanly stop.
- Once the service(s) is/are stopped you can update the DLL.

Note of caution there are 2 versions of the DLL and Anthony had to determine what version I should use. There’s one in the lib\v5 and one in the lib\v6 directories which I assume relate to your OS version. With WHS2011 mine was the v5 one but this may not be correct for your OS. If you’re not sure - DON’T CHANGE IT!

- Once you have updated the DLL (noting the above) you can reboot the server. All should then come up at boot and be using the replaced DLL.

Share this post


Link to post
Share on other sites
19 hours ago, JonnyManiac said:

To fix the DLL issue if it has not been updated:

- Stop any services that might be using the DriveBender volume such as backup software etc.
- Using the Services management console in Windows Stop the ‘Drive Bender Service’. You might be promoted to Stop other dependent services which will be listed, click Yes and let them cleanly stop.
- Once the service(s) is/are stopped you can update the DLL.

Note of caution there are 2 versions of the DLL and Anthony had to determine what version I should use. There’s one in the lib\v5 and one in the lib\v6 directories which I assume relate to your OS version. With WHS2011 mine was the v5 one but this may not be correct for your OS. If you’re not sure - DON’T CHANGE IT!

- Once you have updated the DLL (noting the above) you can reboot the server. All should then come up at boot and be using the replaced DLL.

Thanks for sharing, I'll give it a try...!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...