In order to better support our growing community we've set up a new more powerful forum.
The new forum is at: http://community.covecube.com
The new forum is running IP.Board and will be our primary forum from now on.
This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.
I've just posted a complete tour of DrivePool M4 UI as it is today (dev build).
I guess it's customary to announce things is short form these days, so for those of you who don't like to read too much.
- An awesome new file system, CoveFs, specifically designed for pooling. 100% native, on par with NTFS. No reliance on any user mode service. Needless to say, this is very big.
- DrivePool is now a disk. Yes, it has a drive letter.
- Deeper integration with the Dashboard.
- Usability improvements such as background duplication changing.
- Indexing support.
- Refreshed UI. Read the blog post for more...
What's taking so long?
I've decided to cut loose the open source 3rd party file system used in M3 and write my own specifically optimized for pooling.
As some of you may know, the original plan was for a performance layer to run on top of M3. While implementing the performance layer it became obvious that making this layer be the file system itself would yield enormous benefits such as stability, compatibility and performance.
It would take a bit longer, but after doing some testing it was the obvious choice. I had to write a new kernel virtual disk driver and a new file system. But rest easy, these have been done for a while now. They might need some tweaks before release, but my main focus right now is to bring all the pieces together. I'm shooting for the end of this month for a public release. If I miss it, then it will be Jan.
Overall, it's looking good now. It was a bit of work to get here so hopefully people will find it useful.
Sorry if I was neglecting the forum, but there are so many hours in a day. You can always get in touch with me via. stablebit.com.
What about the conversion from M3 to M4. I had, just today, decided to bit the bullet and install M3 and worry about M4 later since I've assembled all the hardware I need. Since there now is a timeline for the M4 release, I'm back decision table again. What does it take to move from M3 to M4? Is it a fairly easy process in the sense of just uninstalling M3 and installing M4 (which I assume would convert the files to the new CoveFs)?
Awesome looking software by the way, can't wait until the RC is out.
will M4 upgrade over M3?
That is a great overall! I like the deeper integration with the dashboard. I think it will be less confusing for people. Can't wait to try it out with the new UI. Keep up the good work!
I Have been awaiting this news a a long time. Thank you for the information and keep up tye good work
I am currently running with 4 Westerdigital (WD20EARS) green drives and i avg around 30MB/S writing over a wired gigabit network. The only thing i can think of is that mine go through an old LSI raid controller and an Intel SAS/SATA expander wich maybe handle data a little better then just through a MB sata controller.
Deeper integration with the WHS console is another huge benefit. It may be "DriveBender like", but who cares, are you suggesting that he doesn't implement features that his competitors have?
I used DriveBender initially for my new server set up, I did NOT like it. I had major problems setting it up and it never worked quite right for me.
DrivePool has it's problems, but I feel its direction is more in line with what I would like to see in my pooling software so I'm sticking to it. If they can fix:
I have NO problem forking over $40 for this great piece of software.
The files are still stored on the individual disks at standard NTFS files. You can still plug in a pooled disk to another machine to get at your pooled files.
CoveFS is simply the file system that facilitates disk pooling. So when you copy a file to the pool, it goes onto one of your NTFS disks, and the file is completely unaltered. Duplicated files go on 2 disks.
CoveFS doesn't filter I/O or modify I/O that goes to your regular disks. It's not involved there at all. So when you copy a file to a non-pooled disk, CoveFS is not involved in any way."
Like a lot of people using Drivepool....we did try out Drice Bender to find out it has many more issues than Drivepool ! Not to mension the more complicated user experience.