Scuro

I've had this problem as well. Balancing goes around 2-5mbps. If I stop the drivepool service and do the balance manually, I get 200+ mbps. Arrows make no difference for me in speed.

Sorry I guess I do have wildcard file placement rules but I've verified that none of them are restricting placement of my test files that are going to the wrong disk. I'm unsure of the exact date this started happening but it was within the last three months or so. I tried downloading the latest beta, same issues. I uninstalled all balancer plugins as well as ran a drivepool repair (reinstall). Edit: I've also verified that no matter what balance I use, it does not work unless I check "file placement rules respect real-time file placment limits set by the balancing plug-ins". However, if I select this, my file placement rules are ignored. Edit2: Disabling all file placement rules still results with the files not going to the correct drive order listed in "ordered file placement"

I have lots of file placement rules but nothing with a wildcard. My parity drives are much larger than my other disks. I like to take advantage of this and store non array data there (data like redundant backups).

I've noticed recently that the file placement balancer no longer seems to be working. Everything is going to the drive with the most free space (default balance behavior). I tried resetting all settings to default but I still get the same results. Ordered file placement is at the top but set as "only control new file placement". This is my balancing settings. Auto balancing is disabled because I use SnapRAID. I also tried with all balancers unchecked except ordered file placement. Same result. If I turn on "file placement rules respect real-time file placement limits" it works but the placement now ignores my "file placement" rules that tell some data to not got on parity drives.

As an update, I have been informed that the latest beta now includes this feature.

Balancing by used space seems such a basic requirement. It is good practice to balance your data evenly across all drives in case of a failure. Balancing by percentage used would result in much more data loss on larger drives when you have space available on smaller drives.

I'm using SNAPRaid and it would be nice if I could automate balancing by used space by bytes to keep the parity file size optimized. I can't find any options to balance by used space, only by percentage used.

I'll start off that I have already disabled bitlocker_poolpartunlockedetect. "BitLocker_PoolPartUnlockDetect": { "Default": true, "Override": false } However I still get disk activity across all drives every 15-30 seconds or so. When I run Process monitor I see the drivepool constantly making requests across all drives Process monitor shows some results as BUFFER OVERFLOW and INVALID PARAMETER. Is this disk activity normal?

It took all day but I was able to resolve this by forcing the pool to remove the drive it wasn't seeing the files, waiting for it to dump all files, and then remounting the drive.

When I run dpcmd on a file that is missing, I get no errors and it detects it correctly on the drive it is located on PS C:\WINDOWS\system32> dpcmd check-pool-fileparts "D:\Shared\Videos\TV Shows\Andor.S01E01.1080p\Andor.S01E01.1080p.mkv" dpcmd - StableBit DrivePool command line interface Version 2.3.2.1493 Detail level: Inconsistent File Duplication Listing types: + Directory - File -> File part * Inconsistent duplication count ** Inconsistent duplication attributes ! Error Listing format: [{0}/{1} IM] {2} {0} - The number of file parts that were found for this file / directory. {1} - The expected duplication count for this file / directory. I - This directory is inheriting its duplication count from its parent. M - At least one sub-directory may have a different duplication count. {2} - The name and size of this file / directory. Scanning... Summary: Directories: (0) - [Streams: (0) 0 B (0 B)] Directory parts: (0) - [Streams: (0) 0 B (0 B)] Files: (1) 1.85 GB (1,985,633,052 B) - [Streams: (0) 0 B (0 B)] File parts: (1) 1.85 GB (1,985,633,052 B) - [Streams: (0) 0 B (0 B)] File parts by pool part UID: - 75c43772-2ac7-45d8-8f30-0890224ddf51: x1 - (1) 1.85 GB (1,985,633,052 B) [Streams: (0) 0 B (0 B)] This happened after removing a disk from drivepool. The disk was removed via the drivepool GUI. No errors are shown in service logs. I tried uninstalling drivepool, rebooting, and reinstalling. Files are still missing. How do I force drivepool to correctly detect these files?

I downloaded and installed the latest beta because of failed duplications with a VM. I've since moved the VM off of drivepool. However drivepool will only load the UI on first boot and then fail to show it afterwards. Task manager shows Drivepool.ui.exe running in the background multiple times if clicked more then once. I'm not sure if this is a known issue. Drivepool is installed on a device running windows 10 1909

As an update I was able to narrow down where the problem occurs. innodb_temp_data_file_path=/temp/ibtmp1:12M:autoextend:max:1G This variable, if selected on a drivepool mount, will generate the errors: 2018-12-05 11:03:42 0 [ERROR] InnoDB: Operating system error number 24 in a file operation. 2018-12-05 11:03:42 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2018-12-05 11:03:42 0 [ERROR] InnoDB: File \\.\D:: 'DeviceIoControl(IOCTL_STORAGE_QUERY_PROPERTY)' returned OS error 224. And cause instability problems. It defaults to the data directory of your database. If I use a junction to point the temp directory to a directory outside of the pool it runs without errors. Christopher, you might not be seeing these problems as you may need to have SQL queries that generate temp tables.

I've switched to Linux VMs for MariaDB. However, I still have my old database available to test this again on drivepool. I tested it and it resulted in the exact same errors again. I enabled logging and submitted it just now as described in http://wiki.covecube.com/StableBit_DrivePool_2.x_Log_Collection

Nevermind. I figured it out. I like to run everything as services so service starts and stops are handled automatically and gracefully without logins. I had set many services to have drivepool dependency that stored data on the drivepool. MSI installer doesn't know how to handle the depency even though the service is not restarted till reboot? Anyways, removing drivepool dependencies allowed the update to finish installing. Is it possible for the MSI updater to handle drivepool dependencies so that I don't have to remove them every update?

I am trying to update to latest beta version and every time I try to update, I get 0x80070643 error. Already tried restarting. Log wasn't helpful.

I am on 2.2.0.906 which is newer (the latest release on http://dl.covecube.com/DrivePoolWindows/release/download/). I have "File placement rules respect real-time file placement limits set by the balancing plug-ins." and "Unless the drive is being emptied." unchecked.

Still not finishing it's balance. I believe I can tell why. Based on the balance targets, it is trying to balance my SSD that it is not able to add more data because of file placement restrictions. I only allow a few folders on my SSD. The balance plugin seems unaware of this and tries to balance regardless.

Just an update for this thread, I've updated to the latest version (2.2.0.906) and still unable to get balance to finish. Drivepool will recognize it's unbalanced but will randomly stop balancing in the middle of it's balance task.

Christopher, I have submitted another troubleshooter report to avoid confusion. I made sure mariadb was back on the pool before submitting. The errors returned again after moving it back to the pool. I moved it back off the pool after the troubleshooter was submitted.

Thanks for your help B00ze. I however believe that is a Linux OS error code. Windows seems to have a limit around 17 million open files.

I submitted the troubleshooter with the requested ticket ID in the thread I linked. Was that data lost or never make it?

Thanks for your time Christopher. I already submitted a troubleshoot report in this thread: I am not sure if it would just be redundant for me to submit another. In that thread I had thought my problems were because of a new power supply I had gotten around the time the errors first started happening. After thinking about it, I remembered I switched the mariadb database to drivepool at roughly the same time I got the new case/power supply. So it should contain all the same data as mariadb was still on the drivepool at the time the troubleshooter was run.

Windows 10 Pro version 1709 with stablebit 2.2.0.904 RC. I have had zero problems and errors after moving the database off the drivepool. I had been hammering my head trying to figure out where all these IO errors were coming from and had thought it was a power supply in another thread (every drive was throwing IO errors in event log). Turns out I was getting those IO errors because every drive was part of the pool. Once I removed mariadb from the pool, it has been running flawlessly. Due to the instability of the OS as well as IO errors in event log, I don't believe incorrect permissions for a database would lead to OS hardlocks (no BSOD, computer would become unresponsive with hard drive LEDs stuck on). Server uptime is now 4 days 13 hours with zero reported disk errors or mariadb errors. EDIT: I was able to move VMs back without issue. It's some kind of conflict with mariadb and my database on drivepool with duplication.

Apache/PHP were also throwing errors at random for parse_ini_file() saying "parse_ini_file failed to open stream" when duplication was enabled. Placing the ini file used for the script outside of the pool on the same drives that were duplicated in the pool solved that problem as well. Edit: The drives that were used in the the drivepool for the database were SSDs that one shares with the OS and the other VMs. Neither have shown problems outside of using drivepool for mariadb or apache/php files with duplication enabled.

Have you tested it with folder duplication? I have tested it outside of the pool now on the two drives I had it duplicated on with the exact same permissions. Both drives have completely solved all instability errors and problems if I use the database outside of the pool. The errors come back immediately if I copy it to the drivepool.