Jump to content
Covecube Inc.
  • Announcements

    • 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. 

Search the Community

Showing results for tags 'limitations'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Covecube Inc.
    • Announcements
    • Nuts & Bolts
  • BitFlock
    • General
  • StableBit Scanner
    • General
    • Compatibility
    • Nuts & Bolts
  • StableBit DrivePool
    • General
    • Hardware
    • Nuts & Bolts
  • StableBit CloudDrive
    • General
    • Providers
    • Nuts & Bolts
  • Other
    • Off-topic

Found 3 results

  1. In the advanced settings of Plex Media Server for transcoder, setting the Transcoder temporary directory to a folder in a DrivePool causes Plex to show an error on playback. I wanted to check if anyone else has that behaviour, if so, maybe include that in the limitations. Also, perhaps a general guideline would be to put "cache" folders outside of Drivepool? ____________________________ EDIT: It looks like it works, the problem were due to some other error that caused the DrivePool to go in read-only mode (which a reboot fixed).
  2. Blockchain Data OK on DrivePool?

    Is blockchain data OK to be stored on DrivePool? As opposed to directly on the hard disk (metal). Examples: Bitcoin Core Bitcoin Armory Ethereum Mist
  3. StableBit DrivePool Known Issues and Limitations

    Due to how StableBit DrivePool and certain software works, there are some known limitations. Stable Release: 2.1.1.561 Public Beta Release: 2.2.0.852 VSS Support. This includes anything that strictly requires VSS support to work. This includes (but is not limited to): Windows BackupYou can back up the pooled drives, but not the pool directly. Windows Server BackupYou can back up the pooled drives, but not the pool directly. Previous Versions System Restore Dynamic Disks. Because of the added complexity of Dynamic disk, we don't support them being added to a pool. Specifically, we take into account the physical disk when determining where duplicates reside, and that adds a lot more complexity and overhead when you start dealing with Dynamic Disks due to the complex arrays that you can create with them. Plex Media Server's database. This database relies on hard linking files together, instead of using the database to point to the same file for redundant files. Because we don't support hard links on the Pool, you may notice missing images in Plex if the database is being stored on the pool. OneDrive for Windows 8.X. Windows 8 uses a new type of file system link to link the files to the cloud (and locally), in a seamless way. Unfortunately, we don't support this file system link only the pool current. USN Journaling . This may affect how certain apps detect changes on the pool. NOTE: Issues with "Change notifications" has been resolved in the beta builds (2.2.0.651 and up). This affects apps like DropBox. Antivirus Scanners. This is a broad generalization. But due to how they work, they can adversely affect the pool and it's performance, and can even cause some pretty bad behavior (eg, locking the system up).If you suspect that this is the case, version 2.2 and up has the option to disable the "bypass file system filters" feature (located in "Performance", under Pool Options), which may fix this. Otherwise, we recommend completely uninstalling any antivirus program that you suspect is causing issues (disabling isn't enough as the real time scanner is actually still active). Data Deduplication. This mainly applies to the Windows Server role, rather than 3rd party software. This feature works by identifying identical blocks of data. It converts the files into a special kind of reparse point, and carves out the duplicate data. This duplicate data is placed into the "System Volume Information" folder (and may be handled as part of VSS). When you access the data, a file system filter splices the data back together. While not officially supported, it should work on the underlying disks. The public beta build (2.2.0.651 and up) add some handling for Deduplication, so that the data is detected "intact". Deduplication is NOT supported on the pool, and because it appears to use the same data structure as VSS, it may never be supported. TrueCrypt/VeraCrypt. This software bypasses the normal disk API, meaning that it does not show up for StableBit DrivePool, and cannot be used. Permissions issues after deleting folders. This is a weird issue with how the data is deleted, and a timing issue. Resolved in the Public beta build (2.2.0.651) License stuck on "Transfer license" or stuck on wanting to be activated. This is an issue with reading the settings store, usually. Either a disk issue or corruption issue. Running a disk check ("chkdsk c: /f") or upgrading to the public beta should fix the issue. Resetting the settings manually will fix the issue, until it occurs again (not a guarantee) Measurement issues in version 2.2.0.651 and up. This includes inaccurate data, or "unduplicated" data showing up on pools which are completely duplicated. This has been fixed in version 2.2.0.721 and up, but the fix may adversely affect Deduplication data from being show properly. A complete remeasure of the pool will be performed after installation. Two reboots required after installation/upgrade on Windows 10 and Server 2016. This is due to an issue with the Windows Installer service, as it incorrectly identifies Windows 10/Server 2016 as Windows 8/Server 2012(R2). The service correctly identifies the system and installs the correct driver, but this requires an extra reboot. This has bee fixed in 2.2.0.723 and up. ReFS. Not supported at all until the Public Beta (2.2.0.651). Additionally handling has been added, but at this time, full support does not exist. By "Full support", we mean registering the Pool drive as ReFS instead of NTFS, integrity stream support, and potentially additional handling for ReFS (such as checking integrity streams, and reduplicating files for "bad" files). It should be noted that ReFS only enables integrity streams for drive metadata. If you want to enable it for all files, you need to run "Set-FileIntegrity X:\ -enable $true" from a powershell prompt Long File Paths. StableBit DrivePool doesn't have a problem with log paths, and actually supports long paths (up to 64k character paths, I believe). Explorer, however uses win32 API and does not support long paths.There is, however an issue where file names (not paths) longer than 200 characters cause issues. This is resolved in 2.2.0.684. Pool is Removable. This is default behavior, but causes issues with some software, and may be a problem for some people.The Public Beta build (2.2.0.651) disables this behavior by default, and introduces an advanced setting that can be used to toggle the setting. Files not showing up in directory list. There are actually a number of causes to this. However, we did discover a bug that was (in rare cases) causing the directory listing to prematurely stop. This was fixed in 2.2.0.683If you are on this build or later and still are experiencing this issue, then the issue may be network related. By default, Windows caches network information, such as directory searches. This can cache the incomplete list. In this case, the fix is a simple registry tweak: http://wiki.covecube.com/StableBit_DrivePool_Q7420208 This will increase network usage slightly, but should not adversely affect the network. XCOPY, RoboCopy and other utilites error out when copying to/from root directory. This is a known issue wit the Release/Stable version. Fixed in the Public Beta version (2.2.0.651). Spontaneously losing duplication. Eg, the pool becoming unduplicated, or otherwise showing a smaller size than expected or set to. This is an exceedingly rare issue, and a very odd one. It shouldn't not appear in the latest betas, as a bunch of error handling has been added to specifically watch for this. Recommended to grab the latest beta (2.2.0.734) Cannot add VHD(X) based disks to the pool. Errors out when trying to add a drive that is a mounted VHD(X) file to the pool. Error or long delay when renaming folders on the network. This applies to Windows 10 Anniversary update (version 1607) as the client, and Windows Server 2012R2, Windows 8.1 and up as the share server. There is an issue when the share has been indexed locally on the server by Windows Search. This is NOT a StableBit DrivePool bug, but a bug with Microsoft code. For now, the solution is to disable the Windows Search service. However, if you're using Windows Server Essentials, this will adversely affect the built int streaming options, as well as the file list for the Remote Access Website. Microsoft KB Article: https://support.microsoft.com/en-us/kb/3198614 You can "fix" this issue here: Q542215 Cumaltive update that addresses this issue is available here: Link Cannot Remove Drive, "access denied" error when attempting. This applies mostly to the internal betas, as it is a bug that was recently introduced. The latest betas fix this issue (fixed in 2.2.0.739 specifically) This list is by no means comprehensive, and it's contents may change as these issues are investigated. Internal Beta builds can be found here: http://dl.covecube.com/DrivePoolWindows/beta/download/ The latest, safe build is 2.2.0.870 Full change log can be found here: changes.txt Don't download the latest build unless instructed to, especially if it's not a listed numbered build in the change log, as these are interim development builds and may not be stable.
×