http://www.vilett.com/disParity/forum/ disParity: Recent Posts en Mon, 06 Sep 2010 07:55:00 +0000 http://www.vilett.com/disParity/forum/topic.php?id=59&page=2#post-696 Sat, 04 Sep 2010 07:52:59 +0000 Neostim 696@http://www.vilett.com/disParity/forum/ <p>The Intersect drive is working great! (In read only mode, haven't tried any writes). One question though, would it be possible to have it running as a service, so one doesn't have to have the command prompt open while it runs? </p> http://www.vilett.com/disParity/forum/topic.php?id=59&page=2#post-695 Fri, 03 Sep 2010 10:01:47 +0000 Neostim 695@http://www.vilett.com/disParity/forum/ <p>Awesome! I can't wait to get home and test both of these, and check out the source code :D </p> http://www.vilett.com/disParity/forum/topic.php?id=59&page=2#post-694 Fri, 03 Sep 2010 09:05:12 +0000 Smurf-IV 694@http://www.vilett.com/disParity/forum/ <p>@fpdragon<br /> Have you tried rename for a directory as well ? (Just thought of that)<br /> The delete directory and rename if spanned would also affect my interpretation of this "Pooled" view as well.</p> <p>Yes Lets work on this together, have you joined codeplex yet ? </p> http://www.vilett.com/disParity/forum/topic.php?id=59&page=2#post-693 Fri, 03 Sep 2010 03:21:18 +0000 fpdragon 693@http://www.vilett.com/disParity/forum/ <p>Would be good to collect all information by joining one project.</p> <p>I just had the first issues with IntersectDrive 0.2:<br /> I can't save a file which was open and changed from a virtual drive. Have to choose "save as" and use an other file name. Also file renaming isn't working.<br /> But: A direct copy to a virtual drive is working. Same if you copy from virtual to virtual drive.</p> <p>And a little bug: If a folder is on two disks (shown as one on the virtual drive) and you try to delete it, the folder is only deleted on one disk. You have to redo the deletion as many times as the folder is present on the disks. </p> http://www.vilett.com/disParity/forum/topic.php?id=59&page=2#post-692 Thu, 02 Sep 2010 09:33:45 +0000 Smurf-IV 692@http://www.vilett.com/disParity/forum/ <p>@fpdragon &#38; @freehand &#38; @Lay<br /> OK. anything x64 is a problem with the installer logic, in that it is trying it's best to find out if 0.5.3 is installed. I made an incorrect assumption (Which come to even type it is really a noob error) that the x64 driver would be the same size (It could have been in the system 32 SxS equivalent) as so the installer throws a wobbler.. I'll correct that .. Soon.<br /> I had previously already created a "ticket" on the Dokan issues stating that the version that is installed cannot be checked for.<br /> So I am in the process of creating x64 images, and then will perform some tests and create a new installer. Please keep an eye on the <a href="http://liquesce.codeplex.com/" rel="nofollow">http://liquesce.codeplex.com/</a> site.</p> <p>@freehand<br /> Yes, I would really like to have you on board, perhaps we can nail this dokan thing together and get a really simple solution out there.. </p> http://www.vilett.com/disParity/forum/topic.php?id=59&page=2#post-691 Wed, 01 Sep 2010 23:02:01 +0000 fpdragon 691@http://www.vilett.com/disParity/forum/ <p>Hi!<br /> I just tried out IntersectDrive 0.2 and I have to say that it's working without any problem on my multiple TB Win7 x64 machine. Also network shares are working, and the "add to free space" feature is cool.<br /> some things I am missing in the app:<br /> * Possibility to generate 2 virtual drives (one for data and one for backup ;)<br /> * custom cache directory (for my ssd ;) to speed up the write process.<br /> some questions:<br /> * how did you manged file resizes on nearly full disks? Do you balance the data on the disks or do you fill one disk after the other (and leave some space for file resize / how much?)?<br /> --* balanced would make it easier to defrag the disks and won't have a problem with file resizing ;)<br /> * where do I get the newest version? (website? project page?)<br /> * is there a way to get the source code to help and improve?</p> <p>liquesce can't be installed on my Win7 x64 because of the same error like freehand reported. Since IntersectDrive works I would say that it isn't a Dokan problem as sayed during the install. I'd love to see another try of this app too but IntersectDrive runs already stable on my pc. </p> http://www.vilett.com/disParity/forum/topic.php?id=59&page=2#post-690 Sun, 29 Aug 2010 15:56:17 +0000 freehand 690@http://www.vilett.com/disParity/forum/ <p>Finally updated the IntersectDrive today. You can get the new version here: <a href="http://server.ktrace.com/IntersectDrive_0.2.zip" rel="nofollow">http://server.ktrace.com/IntersectDrive_0.2.zip</a></p> <p>It now supports folder merging and renaming, etc.<br /> Read only option is fixed now as well.</p> <p>Smurf-IV looks good! I was just about to start work on a GUI for my app but maybe we should just work together. I like where you are going with liquesce! Exactly what I was gonna do. I downloaded it but I can't seem to install it. It keeps saying "This application requires Dokan Ver 0.5.3.". Not sure why it is complaining as I have it installed already. Any ideas?</p> <p>UPDATE<br /> I downloaded the source and I was able to run it fine in Visual Studio. I will have to check your installer logic to see what it is doing. </p> http://www.vilett.com/disParity/forum/topic.php?id=59&page=2#post-689 Sun, 29 Aug 2010 13:37:25 +0000 Smurf-IV 689@http://www.vilett.com/disParity/forum/ <p>I have started a Similar Project and would not mind some help and possibly some testers for it<br /> <a href="http://liquesce.codeplex.com/" rel="nofollow">http://liquesce.codeplex.com/</a><br /> It does merge directories, and has a simple GUI to help with the initial layout.<br /> It seems to be having some trouble (Probably the Dokan Library !) with Notepad and Meta&lt;Browser&gt; on Win 7 Hosts being accessed via a share to the mounted drive, at the moment, but then I still class it as Alpha (I'm using it but) it needs testing in more environments with hosts and clients being different etc.<br /> Please Add Discussions and Issues and possibly some patches as well.</p> <p>Cheers </p> http://www.vilett.com/disParity/forum/topic.php?id=102#post-688 Tue, 03 Aug 2010 08:09:46 +0000 Roland 688@http://www.vilett.com/disParity/forum/ <p>Yes disParity always returns 0 no matter what happens. I'm not actively working on disParity at the moment (current version is stable) and I'm probably not going to put out a new release right now for such a small change, but I'll put it on the list of things to include when I do get a new version out.</p> <p>-Roland </p> http://www.vilett.com/disParity/forum/topic.php?id=59&page=2#post-687 Mon, 02 Aug 2010 12:18:26 +0000 hansdavid 687@http://www.vilett.com/disParity/forum/ <p>I have tested it and it works as it should. Good work! The only wish I have is the ability to merge to shares with equal root directory structures (e.g. making it possible to have a directory spanned over multiple shares) </p> http://www.vilett.com/disParity/forum/topic.php?id=102#post-686 Mon, 02 Aug 2010 09:57:14 +0000 hansdavid 686@http://www.vilett.com/disParity/forum/ <p>Hello.</p> <p>I think I will use this excellent tool to add parity to my disk setup. I use Win 7 and want to add a daily update task. This can be done using the Win 7 scheduler. What I would like is that an email is sent if the update was unsuccessful or similar. That could be achieved if disParity either could include an email functionality or that it return a code (e.g. 0 is successful and not 0 if unsuccessful). Then it is possible to check the return code and send an email if an error is encountered. The tests I have done only indicates that disParity always returns 0. Is that correct?</p> <p>Kind regards, Hans-David Alkenius </p> http://www.vilett.com/disParity/forum/topic.php?id=71#post-685 Thu, 29 Jul 2010 13:23:28 +0000 Roland 685@http://www.vilett.com/disParity/forum/ <p>Welcome vapoured, hope you find disParity useful. I'm currently using it to protect almost 8TB of data (!) </p> http://www.vilett.com/disParity/forum/topic.php?id=71#post-684 Thu, 29 Jul 2010 09:16:00 +0000 vapoured 684@http://www.vilett.com/disParity/forum/ <p>Excellent to hear this simple little program works so good, cant wait to give it a thrashing :P </p> http://www.vilett.com/disParity/forum/topic.php?id=44#post-683 Thu, 29 Jul 2010 09:12:50 +0000 vapoured 683@http://www.vilett.com/disParity/forum/ <p>Well this topic looks dead, but I'm thankful that it existed.. Just reinstalled my server according to that flexraid topic go get it opperating with WHS,<br /> 5x1TB Data<br /> 1x1TB Parity<br /> Test time soon.</p> <p>I'd love to know if anyone else here got their system running nicely with disParity and WHS DE</p> <p>- Vapoured </p> http://www.vilett.com/disParity/forum/topic.php?id=59#post-682 Thu, 29 Jul 2010 07:01:59 +0000 Neostim 682@http://www.vilett.com/disParity/forum/ <p>Sounds good, thanks! </p> http://www.vilett.com/disParity/forum/topic.php?id=59#post-681 Thu, 15 Jul 2010 06:07:20 +0000 freehand 681@http://www.vilett.com/disParity/forum/ <p>Viewing and writing both work. It is the rename that might have some issues... I can't remember. Dokan released a new version of their virtual drive driver... I am gonna try updating to that and add try to clean up the program a bit more. No more console app! Maybe a windows service with a tray icon app or something. Hopefully I can get you guys a new version that you can test. </p> <p>Finding the time to work on this stuff is always the problem! </p> http://www.vilett.com/disParity/forum/topic.php?id=101#post-680 Wed, 07 Jul 2010 08:12:53 +0000 Roland 680@http://www.vilett.com/disParity/forum/ <p>Yes, this is correct. Deleted files risk being unable to recover any lost data on other drives that overlaps with the deleted files. Added files only risk losing the files that were just added.</p> <p>Personally, I just manually run disParity (via a desktop shortcut) whenever I'm done making changes to my media server, regardless of what the changes were. </p> http://www.vilett.com/disParity/forum/topic.php?id=59#post-679 Wed, 07 Jul 2010 06:51:44 +0000 Neostim 679@http://www.vilett.com/disParity/forum/ <p>Bump... Last Chuck episode this season was AWESOME .. haha</p> <p>freehand, I find I CONSTANTLY am wanting a view to show all drives as one..I'm going to play around with your app again, if memory serves me right, the VIEWING of the drives was fine, just not the writing.</p> <p>Any progress on your app, or willingness to release the source code? </p> http://www.vilett.com/disParity/forum/topic.php?id=101#post-678 Wed, 07 Jul 2010 06:40:43 +0000 Neostim 678@http://www.vilett.com/disParity/forum/ <p>Roland can give you a perfect answer, but as for my understanding:</p> <p>Correct, update immediately after deleting/changing.</p> <p>If you delete files, then lose a drive, I believe you can still recover, but you will have gaping holes in your parity equivalent to those deleted files, so when you went to recover, you would be missing a lot of data/have corrupt files.</p> <p>Maybe Roland can answer this.. but I never setup an automatic update for disParity for fear that right when the update is being kicked off, I might add/change files on the drives, causing the parity to be incorrect. I guess if your doing this at 3am it's not a big worry. </p> http://www.vilett.com/disParity/forum/topic.php?id=101#post-677 Tue, 06 Jul 2010 14:42:20 +0000 jje4th 677@http://www.vilett.com/disParity/forum/ <p>I just want to confirm I'm understanding the disparity parity calculation correctly. When I DELETE files I should update right away otherwise if I lose a drive (other than the one where I deleted the files) I WILL NOT be able to recover because the parity data will be out of sync with the files.</p> <p>However, if I ADD files and lose a drive before updating, I WILL be able to recover, just not the recently added files. </p> <p>(And changed files is like deletes, but I don't really change the files so this isn't a concern).</p> <p>My plan is to run update once a week automatically and manually update any time I manually delete files from the protected data set. I am OK with putting a week's worth of added data at risk, but want to make sure that this plan is otherwise sound. </p> <p>Thanks! </p> http://www.vilett.com/disParity/forum/topic.php?id=100#post-676 Fri, 25 Jun 2010 00:30:37 +0000 lmaolmao 676@http://www.vilett.com/disParity/forum/ <p>thanks for the fast reply Roland. I'm going to put all my data I want to protect on each drive into a sub folder.</p> <p>Thanks again for making such an elegant solution. </p> http://www.vilett.com/disParity/forum/topic.php?id=100#post-675 Thu, 24 Jun 2010 14:18:59 +0000 Roland 675@http://www.vilett.com/disParity/forum/ <p>Hi lmaolmao,</p> <p>No, unfortunately this is a limitation of disParity right now. On a particular drive you can only protect either the root, or one folder, so everything on that drive you want to protect must be underneath that. (Of course, you *can* technically specify each folder separately in config.txt, but that will create a dangerous situation where you will not be protected if that drive fails, so don't do it!)</p> <p>I believe some users have successfully used a Windows concept known as a junction point as another way to solve this problem. In short, you create a single directory on your drive, called something like "MyData" or whatever, and then under that, you create junction points to the folders that you want to protect. Then you protect the single "MyData" folder in disParity. I haven't tried this myself though so I can't vouch for it completely. </p> http://www.vilett.com/disParity/forum/topic.php?id=100#post-674 Thu, 24 Jun 2010 11:01:47 +0000 lmaolmao 674@http://www.vilett.com/disParity/forum/ <p>Roland,</p> <p>I've only just discovered disParity and I think it's brilliant in it's ease of use!</p> <p>I have a question/feature suggestion:</p> <p>I have 3 data drives and a soon to be parity drive.</p> <p>On the data drives I don't need all the folders to be in disParity.</p> <p>On my first drive I have the following folders:</p> <p>E:<br /> |&gt;TV<br /> |&gt;Movies<br /> |&gt;Photos<br /> |&gt;Documents</p> <p>I would like to use disparity to help protect photos and documents, but not the other two.</p> <p>Is that possible? </p> http://www.vilett.com/disParity/forum/topic.php?id=99#post-673 Tue, 25 May 2010 16:23:01 +0000 Roland 673@http://www.vilett.com/disParity/forum/ <p>Awesome! I love hearing stories like this! :) </p> http://www.vilett.com/disParity/forum/topic.php?id=99#post-672 Mon, 24 May 2010 08:31:22 +0000 rust0r 672@http://www.vilett.com/disParity/forum/ <p>I recently had a drive degrade, file transfers froze, dwindled to transfer speeds of kbit/s, apps using files on the drive crashed, it was not looking good. </p> <p>I plugged in a replacement drive and started the rebuild, a little while later I was up and running and everything was as good as new.</p> <p>Roland, thanks again for all your hard work, it's moments like this that I am amazed at the worry-free nature in which your software allows us to backup and recover our files! </p> http://www.vilett.com/disParity/forum/topic.php?id=98#post-671 Wed, 19 May 2010 12:57:34 +0000 romwarrior 671@http://www.vilett.com/disParity/forum/ <p>Thanks for the info, Roland. </p> http://www.vilett.com/disParity/forum/topic.php?id=98#post-670 Mon, 17 May 2010 08:51:49 +0000 Roland 670@http://www.vilett.com/disParity/forum/ <p>The amount of parity used is only determined by the largest drive in your array... or rather, the drive with the largest amount of used space. So in your case, the media5 drive is the one that is determining that mount of parity used. Even if the other 4 drives were empty, since media5 is almost full, the parity drive would still also be almost full. Since you added the 40GB file on the media4 drive, it makes sense that no additional parity space was used by that file, since it was able to combine the data of that file with parity data already in use.</p> <p>The extra 20GB used on your parity drive is probably due to fragmentation; if you've done a few rounds of deleting/moving/editing files, especially large ones, that could easily chew up an additional 20GB. DisParity will attempt to re-use that fragmented space when it can, but it can't always fit a large file into a small hole. Eventually, with enough updates, you could run out of parity space (especially if you add more data to media5.) If that happens, unfortunately right now the only thing you can do is re-create the parity from scratch, which will remove the fragmentation. </p> http://www.vilett.com/disParity/forum/topic.php?id=98#post-669 Fri, 14 May 2010 12:48:26 +0000 romwarrior 669@http://www.vilett.com/disParity/forum/ <p>Thanks, Roland. I freed up some space on my C drive and the update went through with no errors. However, the free space numbers I listed in my first post have not changed at all after the update. So my parity drive has 20 GB more data on it than any of my media drives. I know there's an overhead but I didn't think there was that much. One of my drives has about 18000 audio files, but the rest have a considerably fewer number of files.</p> <p>So should I be concerned that the free space did not change at all with the inclusion of a 40 GB file? I did delete some files before adding the file, but those went through on a separate update. Does disParity reserve disk space? What about the 20 GB more data on the parity drive? Anything to be worried about? </p> http://www.vilett.com/disParity/forum/topic.php?id=98#post-668 Thu, 13 May 2010 13:54:49 +0000 Roland 668@http://www.vilett.com/disParity/forum/ <p>I believe this error is occurring when disParity is trying to write the 40GB of modified parity data to a temp file during the update, before it copies the final data back to the parity drive. So the drive that is running out of space in this case is the drive that contains the temp data, not the parity drive.</p> <p>By default, disParity writes temp date to its own folder, so this drive would be whatever drive disParity is installed on. You can override the temp location to whatever you like in the config.txt file:</p> <p>temp=D:\Some\Folder\disParityTemp\</p> <p>Try setting temp to a drive that you know has more than 40GB free. It can be one of the protected drives, but for performance reasons I wouldn't recommend that unless you have no other choice. </p> http://www.vilett.com/disParity/forum/topic.php?id=98#post-667 Wed, 12 May 2010 08:21:48 +0000 romwarrior 667@http://www.vilett.com/disParity/forum/ <p>I think this is a different issue than the other disk space thread, but if not you can delete this.</p> <p>I am trying to update a set that I have been updating fine for a few months now. During the last update it would not add one of my files to parity (a 40GB single-file rip of a Blu-ray that I own). The exact error is "Error writing parity data: There is not enough space on the disk."</p> <p>However, my parity disk is the biggest disk. Here is what Windows shows:</p> <p>Drive - Capacity - Free Space</p> <p>Media1 - 1397.26GB - 22.99GB<br /> Media2 - 1397.26GB - 60.34GB<br /> Media3 - 1397.26GB - 220.42GB<br /> Media4 - 1863.01GB - 202.76GB<br /> Media5 - 1863.01GB - 48.41GB<br /> Parity - 1863.01GB - 28.23GB</p> <p>Right now the file is on the Media4 drive but it was originally on the Media5 drive.</p> <p>I am running just a basic WinXP Pro install. I have moved the offending file to a different media drive and get the same error. Windows has no problem moving the file so I assume it is not a file problem. Any ideas? I'd rather not recreate the parity info as that takes about 40 hours. </p> http://www.vilett.com/disParity/forum/topic.php?id=97#post-666 Fri, 23 Apr 2010 03:49:11 +0000 Klaatou 666@http://www.vilett.com/disParity/forum/ <p>Yes it is strange as I don't find that in the logs, I copy pasted the results in the disParity center were I can assure you that it was as you see above ... So the mixe is a disParity center issue ... sorry to "affraid" you with that but as I had all in the center windows I didn't thaught it not could be the real logs.</p> <p>But I still don't understand the verify command gave 0 errors and the test one gave 64 failures for one disk. </p> http://www.vilett.com/disParity/forum/topic.php?id=96#post-665 Wed, 21 Apr 2010 11:00:27 +0000 Roland 665@http://www.vilett.com/disParity/forum/ <p>OK, I think I've got the CAPTCHA working again.</p> <p>Again, if anyone is having problems registering for the forum, just send me an email. Thanks. </p> http://www.vilett.com/disParity/forum/topic.php?id=97#post-664 Wed, 21 Apr 2010 09:50:34 +0000 Roland 664@http://www.vilett.com/disParity/forum/ <p>I can't understand how you would get both the "Test 5785 files" line and the "Verify complete" line in the same log. Those are from two different commands. You should *only* see the "Verify complete" line at the end of a verify command, and not at the end of a "test" command.</p> <p>Can you zip and send me the log that contains the output of the "test" command? Send it to <a href="mailto:rolandv@gmail.com.">rolandv@gmail.com.</a> Thanks. </p> http://www.vilett.com/disParity/forum/topic.php?id=96#post-663 Wed, 21 Apr 2010 09:39:34 +0000 Roland 663@http://www.vilett.com/disParity/forum/ <p>Had to re-enable the CAPTCHA, the spam registrations are completely out of control!</p> <p>So, registration for this forum is now effectively disabled until I can find the time to research this problem more. :(</p> <p>In the meantime, I can register new users manually if you email me at: <a href="mailto:rolandv@gmail.com">rolandv@gmail.com</a> </p> http://www.vilett.com/disParity/forum/topic.php?id=86&page=2#post-662 Tue, 20 Apr 2010 09:39:23 +0000 Klaatou 662@http://www.vilett.com/disParity/forum/ <p>I tried to have 2 parity sets, I had to move a lot of datas to some rep or disks and back. (of course I removed the 4 million files disk ;)<br /> It finished to work (I deleted some reps too), it worked so fine I even retried to have only one parity set and it works, we are exactly in what you said, we have to organized the files and not keep a too big number of files (especialy on the same disk).<br /> Thank you again for your time and ideas. </p>