Jump to content

Christopher (Drashna)

Administrators
  • Posts

    11328
  • Joined

  • Last visited

  • Days Won

    338

Christopher (Drashna) last won the day on June 17

Christopher (Drashna) had the most liked content!

1 Follower

About Christopher (Drashna)

  • Birthday 06/25/1983

Contact Methods

  • MSN
    drashna@live.com
  • Website URL
    https://drashna.net/blog/
  • Jabber
    christopher@covecube.com
  • Skype
    drashnajaelre

Profile Information

  • Gender
    Male
  • Location
    San Diego, CA, USA

Recent Profile Visitors

9669 profile views

Christopher (Drashna)'s Achievements

  1. Shadow Copies is the name for the code/feature that supports Previous Versions, and other features of Windows (such as must backup solutions). It's not part of StableBit DrivePool. That said, if you wouldn't mind, I'd like to take a look at your system directly, and poke around. I may be able to identify and fix the issue a lot faster that way. If you're okay with that, head to https://stablebit.com/Contact and open a ticket.
  2. The simple option, is you don't. Disable shadow copies, and delete them. The System Volume Information will continue to come back (it's a hard coded Windows behavior), but that will reduce the usage. If you run "control system", it's the "System Protection" option. Turn it off and delete them for each disk, in question.
  3. It means that you may have issues accessing data on the pool through WSL. Namely, WSLuses a layer between WSL file system and windows for the file system that can cause issues for DrivePool (eg, potentially unsupported commands, etc). And adding support for it is not simple.
  4. Specifically, the "SSD Optimizer" uses the "drive is being emptied" option, so can if that option is checked (default), it means that the balancers (SSD Optimizer) won't follow file placement rules for the SSD drives, and will empty them, regardless of the rules. Unchecking the "unless the drive is being emptied" means that it will always respect the file placement rules. In both cases, it will still work as a write cache.
  5. As mentioned, there is nothing wrong. It's just that the placement means that duplication can't be used for a large portion of the pool. If you have no plans on using duplication, then you can safely ignore this, and may even want to disable the mentiond "Duplication Space Optimizer" balancer.
  6. Try resetting the permissions on the pool: https://wiki.covecube.com/StableBit_DrivePool_Q5510455
  7. Sorry, no, WSL is still not supported.
  8. https://dl.covecube.com/DrivePoolBalancingPlugins/SsdOptimizer/Notes.txt
  9. Try this: https://wiki.covecube.com/StableBit_DrivePool_Q2150495
  10. Based on the other posts, I'm guessing that file system corruption has occurred on one of your drives ("U:\"), and you need to check for "found.###" folders (run a chkdsk pass, and then check), or run data recovery.
  11. Unfortunately, this is very unlikely to be added, as we have no intention of spreading the contents of files between multiple drives. However, you could use Storage Spaces or RAID, and add that drive to the pool. And you can use the balancers and/or file placement rules to get this sort of behavior.
  12. Is there anythong outside of the PoolPart.xxxx folder on the drive? including shadow copies, lost files restored by checkdisk, etc? Using something like windirstat or wiztree are a good way to find and visualize the data on the drive.
  13. What the error message has said: the data returned does not match what is expected. It has been corrupted or altered, or is using older data from a failover. https://stablebit.com/Support/CloudDrive/Manual?Section=Recovering from Errors
×
×
  • Create New...