Jump to content
Covecube Inc.

Alex

Administrators
  • Content Count

    251
  • Joined

  • Last visited

  • Days Won

    45

Everything posted by Alex

  1. This is a very interesting thread and I think that if there is a performance issue with StableBit DrivePool we need to narrow it down to one particular scenario. For example, as bblue has suggested in the original post, Hyper-V running WHS2011 with a few pass-through drives. As far as some of the other issues that have been raised, let me comment on those: The performance pane uses our file system driver to measure performance with some limited input from the Windows Performance Counters. Some of the earlier BETAs were combining our data with the Windows performance counters in a larger
  2. The Disk Performance area shows the top file operations that are operating on the busiest disks. The file at the top is operating on the disk with the most active I/O request (i.e. the disk which is the slowest to respond because of I/O load). Each file can either be read from or written to, so I guess I'm not understanding the request for showing "write files" vs. "read files". A file can either be written to or read from, it's still the same file.
  3. These are not auto nightly builds but are deliberately built after a Code Change Request (CCR) is completed (see: http://wiki.covecube.com/Development_Status#Development_Workflow). The build process is automatic and the publish is automatic. The difference between these internal BETAs and the BETAs that are published on StableBit.com is that the internal BETAs don't undergo any kind of functional testing before a build is published. The BETAs published on StableBit.com undergo basic functional testing and the installer's upgrade procedure is tested on every supported OS. This takes a bit o
  4. Alex

    Bad Sector

    That's a good suggestion. What the Scanner should probably do IMO in these cases is simply rename the bad file part to something else and let DrivePool's duplication system kick in and reduplicated the file. I'm always worried about deleting files. This way we retain all 3 file parts and the user can delete the bad one. I've flagged this as issue #86 and it will be fixed.
  5. Hmm... could be an optimization issue with the sector map drawing code. I'll take a look at reproducing this right now. We've got an unlinked IAR open for this issue (#88). IARs are our new workflow for handling bug reports and applying fixes. Normally, IARs are linked to contact requests @ stablebit.com/contact so you can get updates on your issues that way. I should really write a blog post about our new internal workflow for handling bugs Oh, and as far as logging performance issues in the UI, yes we do. We have a sort of built-in performance profiler in all BETA builds of the Stabl
  6. You have a good point, there really should be some kind of notification at the end of the removal process. I've added this to the roadmap: http://wiki.covecube.com/Development_Status#StableBit_DrivePool_2.X We will add this to the UI in the future. For now, you can look in the PoolPart... folder on the damaged drive that you just removed. Any files that were not migrated will still remain in that folder.
  7. Bad sectors will get remapped automatically by the drive without your intervention. I've experienced this first hand just a few weeks ago. Here was my experience: A Western Digital Green drive developed a single bad sector. The SMART data confirmed the bad sector that the surface scan has detected. I was notified promptly and began a file scan. The file scan revealed that no files were affected by the damage. At that point I left the system alone for a few hours and then decided to re-check the bad sector to see whether it was still bad. The sector turned green and the SMART data no long
  8. Performance considerations with StableBit DrivePool: For non-duplicated files with the default performance setting enabled, there should be very little overhead for read / write I/O on the pool. This is because all pooled I/O is processed in the kernel and our file system driver uses Neither I/O, Fast I/O, oplocks and a full suite of file caching. These are optional under the hood performance optimizations that are available to all kernel file system drivers and they are all implemented and utilized by our driver. While there is always some overhead introduced by any kind of software storag
  9. Hey guys, I've set up and run a controlled test using the same tool of pool vs. non-pool speeds and StableBit Scanner vs. no StableBit Scanner. Here is how I set up the test server: Server to client connection is on a 1 gigabit link connected through 2 switches. Created 2 shares, one on the pool and one not on the pool. No file duplication enabled. Made sure that the non-pooled share is on the disk part of the pool with the most free space. This ensures that the same physical disk will be used to allocate the test file in both the pooled and non-pooled test cases. Initially, the serv
  10. Alex

    The Roadmap

    As of 1/28/2014, in an effort to streamline the development process and to centralize the management of planned feature requests I've moved the current development status to our development wiki. You can access it here: http://wiki.covecube.com/Development_Status In addition to implementing new features we now have a separate system for identifying and tracking existing issues. See the wiki page for a bit more on that.
  11. For unduplicated files, StableBit DrivePool forwards all file I/O to the individual disk that the file is on. If the file exists on more than one disks (i.e. is duplicated), then: All file modification requests (such as writing to the file, setting its attributes, etc...) go to all of the disks that the file is on. Read requests will either go to the first disk that the file is on (when read striping is disabled), or to one of the disks that the file is on, as determined by the read striping algorithm. A directory listing operation works by querying all of the disks in parallel. This will fo
  12. Absolutely awesome. USB 3.0 and Zotac are amazing. This is why I wrote DrivePool
  13. Alex

    Websites down?

    Yes, absolutely temporary. The stablebit.com server is running on a dedicated Windows Azure box with an automatic DNS failover to another shared hosting account. Today, both failed for about a total of 4 hours. I'm not sure why the Windows Azure services failed, but restarting the servers fixed the problem. The backup host is experiencing a DDOS attack at this time and is still not working. stablebit.com is back up but bitflock.com is still down. I'm monitoring the situation closely. Sorry about the inconvenience.
  14. Today we've had a BitFlock disruption. BitFlock.com was down for about 6 hours becasue of a domain name issues. All access is now restored and you should not experience any further issues accessing bitflock.com. The problem was at Google.
  15. Ok, so after I posted that I realized that I didn't explain at all what I meant in terms of MBits. Most people are aware of Megabytes and Gigabytes (because that's what hard drive space is measured in). I was talking about network bandwidth. Network bandwidth is typically measured in Bits. 1 byte has 8 bits. So in order to convert bits to bytes you need to divide by 8. But the math aside, MoCA is "up to" 100 Mbits /s Which means that it can transfer "up to" 12.5 MB/s. Twelve point five mega bytes per second. Yes, megabytes the same stuff that's on your hard drive.
  16. Mega BITS I know, most people find it very confusing.
  17. I use MoCA myself. It gets close to 100 Mb for me. If you don't need anything faster then it's a great solution.
  18. Kihim, Thanks for uploading the dumps. I've received dumps from 2 people with the same symptoms of stuck on "Initializing", but the issues do not appear to be related to each other. I've made some changes to the code based on both dumps to try and prevent both issues. You can get the latest internal BETAs from here (currently at 2957): http://dl.covecube.com/ScannerWhs2/beta/download/ http://dl.covecube.com/ScannerWindows/beta/download/ I haven't published these yet to stablebit.com because I'm collecting feedback as to whether the fix is effective. Thanks, Edit: Actually
  19. The StableBit Scanner already does a "bus" performance test in order to determine the estimated maximum throughput of the bus that each disk controller is capable of. While we don't do an automatic sequential read / write speed test, I suppose that those could be added. I'll think about how this can be implemented. The upcoming per-folder balancing feature in StableBit DrivePool should let you designate which disks to use for each folder, but that would be a manual task and I understand that what you're suggesting would be completely automatic and not really the same thing.
  20. Alex

    Future Developments

    Future Developments for StableBit DrivePool The current development status for all of our products can now be found here: http://wiki.covecube.com/Development_Status
  21. Alex

    Future Developments

    Future Developments for the StableBit Scanner The current development status for all of our products can now be found here: http://wiki.covecube.com/Development_Status
  22. Future Developments for BitFlock.com The current development status for all of our products can now be found here: http://wiki.covecube.com/Development_Status
  23. Alex

    The Roadmap

    I've been thinking about how I can better communicate what is in store for each of our products, there are 3 now and another one in the works. Starting today I'll be setting up topics in each forum that I'll be updating on a regular basis. Each post will maintain what the future holds for each product. I try to keep a lot of the development driven by user feedback, but most of that feedback doesn't happen in the public forum (but usually in tech support tickets). I'd just like to take this opportunity to highlight the direction that each product is heading in, a kind of roadmap. I'll b
  24. Alex

    File System check

    Yeah, there's something wonky going on here. It should be checking all supported file systems I'm looking into it.
  25. Dough, The first problem that I can see with this is that you may not have enough disk space on the other disks to accomplish this. Filling a disk completely to capacity can cause problems if files need to expand in size. That's why we have the option "Try not to fill a drive above...". Let me explain what should be happening, based on your screenshots: The Disk Space Equalizer runs and redistributes your files equally across all disks. Not considering any other factors. The StableBit Scanner balancer runs and does nothing (since you have no damaged disks). The File Placement Limiter
×
×
  • Create New...