smt52

So, I've proven that a number of existing files were corrupted on the drive, in response to removing 1 of the 3 drives in the DrivePool. I prepared two screenshots which demonstrate this, and a detailed explanation of how to reproduce the error. Essentially, all you have to do is create a program which continuously writes/reads to the existing DrivePool, while removing one of the drives in the pool, and you will see that the files written and read are corrupted. However, when I tried to upload the screenshots, it said "You have exceeded your allotted disk space for attachments". So took that as sign to give up, and not submit any more bug reports. This is a pity, as I put a lot of time into giving you feedback which would help you improve your product (which is excellent in so many other ways, I might add). Perhaps you should increase the amount of space allocated for screenshots to something more than 250 kilobytes?

Hi, I'd like to report what seems to be a bug in StableBit DrivePool. I am running uTorrent connected to drive H:. Drive H: is a DrivePool, which points to drives Y:, X:, and U:. Drives Y: and X: are SATA drives that are internal to my PC. Drive U: is an external USB drive, connected by a high-speed USB 3.0 . I wanted to get rid of my USB 3.0 drive (i.e. drive U:), so I clicked "-Remove". Then, some odd things started to occur. 1. It said "Waiting to remove...Removing..." which looks like a User Interface rendering issue (is your WPF View/ViewModel functioning properly?). 2. More importantly, it suddenly started to claim that some files which I had previously accessed had missing handles, and "Access denied". You can reproduce this by running uTorrent, filling it up with loads of torrent files, then removing 1 of the 3 drives in the pool, and checking to see that uTorrent does not fall over. On further testing, it appeared as if the entire system had started to fall over. At least two programs (uTorrent and MacroExpress) could not save files to H:. I would suggest: 1. Ensuring that while 1 of the 3 drives in a pool is being removed, that the pool itself is still usable. Why should the system suddenly get bad file handles, and unreadable files, and refuse to write files to the pool? 2. When it says "Removing drive ..", give an indication to the user of how long this will take. I don't know if it's going to take 20 hours, or 20 minutes, or another 20 seconds - I'm completely in the dark. And while it's removing the drive, it says "No disk activity on the pool", which indicates that, er, it's crashed or something, and it's doing nothing. This is a bit confusing. I should also add that my system has been running perfectly well for the past 2 years, the machine is a Dell T7500, Enterprise Grade, and as solid as a rock. This is not a hardware issue - it's a software issue.