SOLVED: v4 Erroneous Size Errors for Samba Shares used for Clips and Archiving
I am trying to configure BlueIris 4.0.0.12 to use a Samba share on a Linux ClearOS server for the Clips and Archiving "Stored" directory. The share is 2TB with 90% available. I configured BI to use 300GB. BI now shows an erroneous error in the status display that the available space in the share is only 10GB. I then mapped the share to local z: and configured BI to use it for Stored instead but got the same results. From Windows (8.1) where BI is running, properties on z: show 1.8TB available and I did test write hundreds of GB to the share.
Looks like there may be a bug in BI for calculating available space on network shares. Also, once a share is mapped as a local drive letter in Windows, it is not displayed in the GUI when selecting storage destinations for Clips and Archiving.
I do not know how v3 would handle this as I am a new BI user starting with v4.
[EDIT]
Per fenderman's suggestion I have disabled within BI monitoring of disk space for the offending share. All good now, no red flags or alerts in BI. Of course, the bug is still there as BI does not know how full the drive is.
[\EDIT]
Peter
I am trying to configure BlueIris 4.0.0.12 to use a Samba share on a Linux ClearOS server for the Clips and Archiving "Stored" directory. The share is 2TB with 90% available. I configured BI to use 300GB. BI now shows an erroneous error in the status display that the available space in the share is only 10GB. I then mapped the share to local z: and configured BI to use it for Stored instead but got the same results. From Windows (8.1) where BI is running, properties on z: show 1.8TB available and I did test write hundreds of GB to the share.
Looks like there may be a bug in BI for calculating available space on network shares. Also, once a share is mapped as a local drive letter in Windows, it is not displayed in the GUI when selecting storage destinations for Clips and Archiving.
I do not know how v3 would handle this as I am a new BI user starting with v4.
[EDIT]
Per fenderman's suggestion I have disabled within BI monitoring of disk space for the offending share. All good now, no red flags or alerts in BI. Of course, the bug is still there as BI does not know how full the drive is.
[\EDIT]
Peter
Last edited by a moderator: