![]() ![]() ![]() I presume this means v5.0 is getting CLOSE and know it's been "kicking you" a good bit Although I haven't personally had the bug, I've followed those who do. The free space on drives containing files served up by the share isn't relevant if the share is no longer configured to write to those drives. I believe the free space computation should be the sum of all free space on all drives on which the share is currently configured to write files, minus the total size of files on the Cache drive waiting to be moved to the share. Since the Movie share does contain files on disk2, those files should be included in the consumed space computation. In this case, disk2 free space should be excluded from the free space for the Movie share, since the disk is currently configured to be excluded. Though the share is configured never to write to disk2 going forward Free Space computation for Movie share still includes all free space on disk2,.Switched the Movie share to exclude disk2, but left some movie files on disk2.Later decided to dedicate disk2 to digital photos.Movie share originally had no disks excluded.Tom, thanks again for all your hard work toward 5.0 Final! the recent file integrity bugs were far more critical. I identified one specific issue with the free space computation. I think there is more work to be done however, in handling the used/free space on the cache disk. In rc16c it also includes free space on each disk where it could potentially exist based on include/exclude masks, and whether it's marked cache-only or split=0. ![]() What I fixed was this: in calculating free space for a user share, rc16b only tallied free space on each disk where the share currently exists. Free Space on user shares still seems to behave the same as rc16b. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |