Jump to content
Covecube Inc.
  • Announcements

    • Christopher (Drashna)

      Login issues   11/07/17

      If you have issues with logging in, make sure you use your display name and not the "username" or email.  Or head here for more info.   http://community.covecube.com/index.php?/topic/3252-login-issues/  
    • Christopher (Drashna)

      Getting Help   11/07/17

      If you're experiencing problems with the software, the best way to get ahold of us is to head to https://stablebit.com/Contact, especially if this is a licensing issue.    Issues submitted there are checked first, and handled more aggressively. So, especially if the problem is urgent, please head over there first. 
  • 0
plebann

SSD Optimizer problem

Question

Hi.

I'm using DrivePool with SSD Optimizer plugin (with option Fill ssd drives up to 90%).

I have dedicated partition on my ssd (small, 70GB), SSD Optimizer plugin configured and worked as expected till now.

 

Free space on SSD Partition - 22GB.

Trying to copy one file 43GB to DrivePool Pool (with have 2TB free space) and give error "Not enough free space".

I'm assuming that SSD Optimizer plugin is trying to put new file on my SSD disk, but this file is larger that free space on that disk but - there is still more than 10% free space on that disk and plugin is forcing to place new file on sdd partition.

 

I suppose i'm right because when i disabled SSD Optimizer plugin i was able to copy that file no problem.

 

Is this real issue or i need to improve my SSD Optimizer settings?

Share this post


Link to post
Share on other sites

16 answers to this question

Recommended Posts

  • 0

This is part of the problem with the way that the SSD optimizer balancer works. 

 

Specifically, it creates "real  time placement limiters" to limit what disks new files can be placed on.  

 

 

 

I'm guessing that the SSD is below the threshold set for it (75% by default, so ~45-50GBs).  Increasing the limit on the SSD may help this (but lowering it may as well, but this would force the pool to place files on the other drives rather than on the SSD). 

 

 

Additionally, there are some configuration changes that may help make the software more aggressively move data off of the drive.

http://stablebit.com/Support/DrivePool/2.X/Manual?Section=Balancing%20Settings

On the main balancing settings page, set it to "Balance immediately", and uncheck the "No more often than ever X hours" option, it set it to a low number like 1-2 hours. 

 

For the balancing ratio slider, set this to "100%", and check the "or if at least this much data needs to be moved" and set it to a very low number (like 5GBs). 

 

This should cause the balancing engine to rather aggressively move data out of the SSD drive and onto the archive drives, reducing the likelihood that this will happen.

 

 

Also, it may not be a bad idea to use a larger sized SSD, as the free space on the drive is what gets reported when adding new files. 


This is part of the problem with the way that the SSD optimizer balancer works. 

 

Specifically, it creates "real  time placement limiters" to limit what disks new files can be placed on.  

 

 

 

I'm guessing that the SSD is below the threshold set for it (75% by default, so ~45-50GBs).  Increasing the limit on the SSD may help this (but lowering it may as well, but this would force the pool to place files on the other drives rather than on the SSD). 

 

 

Additionally, there are some configuration changes that may help make the software more aggressively move data off of the drive.

http://stablebit.com/Support/DrivePool/2.X/Manual?Section=Balancing%20Settings

On the main balancing settings page, set it to "Balance immediately", and uncheck the "No more often than ever X hours" option, it set it to a low number like 1-2 hours. 

 

For the balancing ratio slider, set this to "100%", and check the "or if at least this much data needs to be moved" and set it to a very low number (like 5GBs). 

 

This should cause the balancing engine to rather aggressively move data out of the SSD drive and onto the archive drives, reducing the likelihood that this will happen.

 

 

Also, it may not be a bad idea to use a larger sized SSD, as the free space on the drive is what gets reported when adding new files. 

Share this post


Link to post
Share on other sites
  • 0

yeah this made this feature a bit less useful to me that it can't somehow know the size of the file before it writes.  i sometimes have files larger than the spare 32gb ssd i had lying around.  but i can see why you wouldn't always be able to tell the size before you start.

Share this post


Link to post
Share on other sites
  • 0

Hi,

 

I recently converted to W10 from WHS2011, after a few issues :huh: I'm running without too many issues.

 

I had converted a 512GB SSD for use in DP, but although its seen it was not used -

 

Then I discovered I should the use SSD optimizer plug in.

 

I downloaded it, but cant run it.  I get an error message "must use DP 2.xx" to use this version of SSD Opt.  Based on messages here, I'm actually using 2.2.0.852 beta, shouldn't that let me use SSD opt.?

 

If I need to go back to 2.1.1. 561 how do I do it?

 

Also I gained some files that I don't know what they are and can't open them or see size. I'm guessing there is one file for each of my spinners.

 

Is that correct?. .Forum will not let me post a snipit of the folders name, but its a long alpha numeric sequence

 

I duplicate most but not all of my server folders.

 

Please let me know how I can use my SSD.

 

Thanks guys.

Share this post


Link to post
Share on other sites
  • 0

Yeah, sorry about that. The installer that we use (WiX, IIRC) has some odd issues, like this.  

 

And yeah, the new files should copy to the SSD, and then later be balanced off of the SSD, based on your balancing settings. 

 

Also, if you're using duplication, then remember that you need to use 2+ drives for the SSD, or it will fall back to using an archive drive, for duplicated data. 

And yes, this has to be two PHYSICAL drives, not just partitioned drives, as the software is aware of the volume/disk relationships. 

Share this post


Link to post
Share on other sites
  • 0

I did not quite understand this answer as in the part about duplication.

 

As far as I understood, I had not turned on duplication to the 512GB SSD only to the folders on the pool.

 

However, since the files did not later transfer to the pool - it would seem that I need 2x SSD even to store the files and then have them later move automatically move to the spinners in the pool.

 

That's a shame since I have one spare 512GB but only 2x 256GB SSD's

 

So to recap - its not possible to set a single SSD to receive the files and later transfer to the main pool if duplication is set there?

Share this post


Link to post
Share on other sites
  • 0

The reason for this is that we use "real time duplication".  That means that duplicated files are written to all sets of disks, at the same time, in parallel.   Meaning that they're protected as soon as they're written to the pool. 

 

That's why this balancer requires two (or more) drives for the "SSD"s.  

 

 

That said, you can disable real time duplication, and it will then only need the single disk. But it may be a full 24 hours before the data is actually duplicated (protected). So if a disk fails in that time, you may lose data because it's not duplicated yet. 

Share this post


Link to post
Share on other sites
  • 0

That's why this balancer requires two (or more) drives for the "SSD"s. 

 

Really appreciate the quick reply. Pardon me if this information is available in any help file for SSD optimizer.

 

OK, whats the rule about size and number of the SSD's?

 

- If the SSD's are not equal in size, does the optimizer just treat them as both the same size as the smallest?

- How does 3 SSD's work vs. 4? 

- I'm running out of SATA ports, adding them via an add in card is OK for Optimizer?

That said, you can disable real time duplication, and it will then only need the single disk. But it may be a full 24 hours before the data is actually duplicated (protected). So if a disk fails in that time, you may lose data because it's not duplicated yet. 

 

So I could just turn off real time Dupe.  Thought I did that, but 48hrs later files were still on SSD and had duplicated there just like your warning.  I'll try again before deciding on adding another SSD.

Share this post


Link to post
Share on other sites
  • 0

You're very welcome! 

 

No rule on size.  But the size is heavily influenced by your needs.  If you're dumping 100's of GB per day, then you will definitely want larger drives. But if it's more like GBs per day, then a small size is going to be fine. 

Also, the size of the drive has to be large enough to fit the files. So if you plan on dumping 100GB files, then you need a drive that is larger than that, otherwise, you will get "out of space" errors when copying files.

 

 

As for number, the minimum is the highest level of duplication that you're using, generally speaking.  Since you want all of the copies written to the SSD first.... that's a requirement.  If you turn off real time duplication, then you only need one, really. 

(also, see below)

 

If the SSDs are not equal in size, that's fine.  DrivePool's default placement strategy is to place files on the drive with the most free space. This also applies to the SSD Optimizer, and the drives marked as "SSDs".   So, it will round robin between the drives, spreading out the data, if possible.

 

 

As for a controller card, absolutely!  And I have a number of recommendations depending on your budget (more is better here, to be honest). 

 

 

As for the files still being on the SSD, that depends on the balancing settings you' configured.  Also, make sure that the drive *is* marked as an SSD in the balancer, and that nothing has the file open (as this will prevent balancing).

Share this post


Link to post
Share on other sites
  • 0

So in another thread you will see I ran into problems adding 2 older 256GB SSD's. :rolleyes:

 

Anyway after a complete OS install and after there is resolution of my folder questions, I will be following your information above.

 

I will probably add a 2nd 500GB SSD for simplicity and to avoid the driver issues that started my problems, but its good to know you thought ahead on these points.

 

Before I read this reply, I have to admit I "cheaped out" on a SYBA SI-PEX40094 PCI-E  add-in card SATA card, but fortunately it will only have to work with an occasional use optical device unless I add another "Red" in a year or 2.

 

:unsure: Maybe I will try an SSD on it for the sake of science... and let you know.

Share this post


Link to post
Share on other sites
  • 0

I will probably add a 2nd 500GB SSD for simplicity and to avoid the driver issues that started my problems, but its good to know you thought ahead on these points.

 

Before I read this reply, I have to admit I "cheaped out" on a SYBA SI-PEX40094 PCI-E  add-in card SATA card, but fortunately it will only have to work with an occasional use optical device unless I add another "Red" in a year or 2.

 

:unsure: Maybe I will try an SSD on it for the sake of science... and let you know.

 

So far the above card no workee - I'm not sure I want to spend big $ for SATA ports but would be happy to learn of cards you found worked.

 

Maybe move to new thread?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×