Jump to content
Covecube Inc.

Alex

Administrators
  • Content Count

    251
  • Joined

  • Last visited

  • Days Won

    45

Everything posted by Alex

  1. Unfortunately not yet, but it's on the todo list and we'll add it eventually. As soon as that file is opened, the balancer aborts and rolls back whatever it was doing, and the application proceeds to open the file as if nothing else had the file open. The application never gets an error. Background duplication / rebalancing cannot move files that are in use. However, background duplication typically only runs when changing the duplication level of existing files. Once the duplication level change is complete, any further real-time changes to those files are simply written to all file parts
  2. I can think of 2 possible explanations: Build 420 has an issue where if you would keep the performance pane open for an extended amount of time, and the CPU was on the lower end, it would erroneously turn off performance gathering in order to save CPU cycles. This has since been fixed in the latest builds. Your Windows performance counters are corrupt. We've seen this before, and it does cause the performance UI to stop working, Not much we can do about it, except to instruct you to repair those performance counters.
  3. Before moving anything, set up the folder structure in DrivePool as it is in WHS v1 (including folder duplication). Then just move your files into the folders that you've created. Having multiple file parts in the same path is not a problem for DrivePool, as long as the folder is set to be duplicated.
  4. The manual has some good info on this, and you can check out the Read Striping section in this blog post: http://blog.covecube.com/2013/05/stablebit-drivepool-2-0-0-256-beta-performance-ui/ This explains what the different colors mean.
  5. I run VMWare / Virtualbox and have run Hyper-V on and off from the pool. I test and develop DrivePool on the pool. There have been issues in the past that were causing problems with virtualization products, but those have since been resolved. The latest 2.1 builds work beautifully for me. For writes there is no "read striping", writes go to all the disks at the same time (I think you may be getting confused between reads / writes).
  6. Yes, and for future reference, the link to the IAR always contains the version number under "CCR Implemented in". So that's why I post that link as well. For every code change request that I complete, I make a build and put the build number in the IAR.
  7. Confirmed and fixed. Thanks guys, nice catch. IAR: https://stablebit.com/Admin/IssueAnalysis/3204 Download: http://wiki.covecube.com/Downloads
  8. DrivePool.Notifications.exe is responsible for checking for new versions and showing notifications of any kind in the system tray. You can disable it if you don't want any of these functionalities. You can modify the registry as Christopher had suggested, or use autoruns from Microsoft to manage startup items: http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx It's found in the Logon tab in autoruns.
  9. I'm trying to clearly define the problem here. As far as I understand, when you access any share on the pool (from a remote client computer?), all of the drives spin up? As far as having a server side cache, we already do, and a client side cache in the form of oplocks (this means that the server isn't even contacted over the network for some I/O operations).
  10. All internal builds are automatically made available on the development wiki: http://wiki.covecube.com/Downloads
  11. I see what you're saying, I was thinking about the first case specifically. You're right this would not work. With this setup you would end up with conflicting rules that will cancel themselves out. I'll think about how we can solve this.
  12. Yeah, that should work. The Ordered File Placement plugin uses real-time file placement limits to determine which disks get new files and the File Placement balancer will respect those limits by default (unless you change that). The file system should respect both rules as well.
  13. From a technical point of view: For reads and writes, CoveFS just forwards the I/O down to NTFS and the request continues down the driver stack as normal. There should be close to zero overhead. The only long running background task that CoveFS performs is a "measuring" pass. It will enumerate all the files on the pool and compute size statistics. When this is occurring, you will see that in the UI under the "Pool Organization" bar as "Measuring...". The most expensive operation that CoveFS performs, in terms of CPU cycles, is a file open / create. So theoretically, if you had a few processe
  14. Alex

    NFS on WHS 2011

    The .MSI installers are there for managed deployment scenarios. They shouldn't be used normally. The .EXE is really a wrapper over the .MSI (using WiX Burn, which is used by Microsoft as well).
  15. Good to know that a Refresh worked. The problem was technically with .NET, and unfortunately on Windows 8+, .NET is part of the OS and you can't Repair it. If the same issue occurred on Windows 7 you would simply run the .NET installer in repair mode. But because .NET is integrated into the OS on Windows 8, you have to repair the whole OS.
  16. Alex

    NFS on WHS 2011

    That's the problem. When you boot without StableBit DrivePool installed the pool drive is not there and NFS can't find its shares. We do support upgrading by simply installing over an existing version (except when upgrading from 1.X to 2.X). Can you elaborate as to why you can't upgrade by simply running the new installer? Is there an error that comes up? What do you see? Thanks,
  17. We're trying to get there. My goal is to get 2.X to a similar level of Dashboard integration as 1.X. It's a lot more difficult though because 2.X supports many more Operating Systems. But yes, that's the goal. For now, 1.X is still being made available and supported.
  18. The pool is simply a combined view of all the hidden "PoolPart..." folders on each drive that is part of the pool. If you go into each hidden PoolPart... and delete the folder from there then StableBit DrivePool will have no issue with that. However, if the folder contains files then you will want to perform a "Re-measure" task afterwards. That's available under pool options, and it will update the statistics. But I'm curious how you managed to create a "phantom folder" in the first place?
  19. The first time that you turn on duplication on a folder StableBit DrivePool will go through each file in that folder and make a duplicated copy, in the background. It cannot make background duplicated copies of files that are in use, so I suggest that you don't run your torrent client until this is complete. Once the initial background duplication pass is complete, any further changes to those files and any new files created in that folder will be duplicated in real-time. From this point on you don't have to worry about in-use files, as that has no effect on real-time duplication. No, to
  20. This should now be fixed in build 517. It wasn't saving the order if that was the only thing that changed about the rules. Download: http://dl.covecube.com/DrivePoolWindows/beta/download
  21. Yep, we can add that. We don't measure actual physical disk performance as of right now in a way that we can use like that. I would hate to make the user run through a manual test, it really should be automatic. Ah, if I understand you correctly, they actually do remove themselves. For folder based rules, "meaningless" rules are not saved. So a rule with all drives checked will never be saved, even though it is temporarily created while you are in the Folders interface. I'll think about changing the code to respect this. IMO, apply causes confusion I try to avoid that paradigm.
  22. I am absolutely thrilled that you like it. It has been my pleasure. But keep in mind this is still a BETA (wait until you see what's coming up next)
  23. Thank you, it was a bit of work but worth it. It could be a bug. Can you take some screen shots before you click save and what you see after? Needless to say, I don't see that over here.
  24. Alright guys, starting with build 511 file placement rules will no longer include added drives by default. There is now a new option to enable that on a rule by rule basis. I've also added the ability to rearrange folder based rules, as long as you don't break folder depth rules. See attached image to illustrate what this looks like now. Download: http://dl.covecube.com/DrivePoolWindows/beta/download/ Edit: Multiselect implemented in build 512.
×
×
  • Create New...