disParity: Recent Topics

disParity: Recent Topics http://www.vilett.com/disParity/forum/ disParity: Recent Topics en Mon, 06 Sep 2010 07:25:37 +0000 Neostim on "Show all drives as one?" http://www.vilett.com/disParity/forum/topic.php?id=59#post-287 Sat, 26 Sep 2009 05:57:55 +0000 Neostim 287@http://www.vilett.com/disParity/forum/ Hello there, I came accross this software yesterday (after my RAID5 died :( ) and I'm really liking the concept, my only problem is I'm used to having one logical drive storing TB's of data, and I'd rather not have to maintain 4 separate TB hard drives distributing files among them. Is there any way of grouping them together to appear as one drive? Creating any type of volume in windows wouldn't work with disParity I don't think, as disParity needs the drive letters to work off of. If there is any method of software you could tell me about, that would be GREAT! Thanks! hansdavid on "Return code after task (e.g. update)" 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/ Hello. 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? Kind regards, Hans-David Alkenius Neostim on "Drive dead, running recovery" http://www.vilett.com/disParity/forum/topic.php?id=71#post-437 Mon, 28 Dec 2009 13:28:13 +0000 Neostim 437@http://www.vilett.com/disParity/forum/ Well, the inevitable happened, my oldest drive keeled over, a 500GB IDE drive that I had my TV Shows on. Disparity is performing a recovery right now, my only worry is I know I added a couple things to one drive, and I don't think I ran an update, but I don't think I deleted anything without running an update, I guess I'll see! One thing I noticed...disparity isn't writing log files to it's folder.. not since when I first used it in september..so I'm worried if it does miss a file I won't know about it (since it's only outputting to terminal). Anyhow, thanks again for Disparity! It's on season 3 of Battlestar Galactica already! fatchowmein on "Has anyone tested disParity with WHS?" http://www.vilett.com/disParity/forum/topic.php?id=44#post-186 Sat, 07 Mar 2009 04:20:00 +0000 fatchowmein 186@http://www.vilett.com/disParity/forum/ I was wondering if disParity would work with WHS? Does disParity create parity bits on just the parity drive or does it create most of the parity bits on the parity drive but also some bits on the other drives? The reason I ask is because once a physical drive is added to Windows Home Server's drive pool, it seems locked down by the O/S (and no drive letter). I could remove the drive from the pool but I think once I add it back WHS reformats it. I'm hoping disParity has the ability to create a parity bit drive without the need of adding bit information on the other drives. I don't mind if the parity drive dies and my all my drives have to be scanned to recreate the replacement parity drive. One feature of WHS that I dislike is folder duplication and disParity seems to be the perfect solution for what I want. Thx jje4th on "When to update?" 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/ 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. However, if I ADD files and lose a drive before updating, I WILL be able to recover, just not the recently added files. (And changed files is like deletes, but I don't really change the files so this isn't a concern). 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. Thanks! lmaolmao on "Specify Folders Within A Drive?" 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/ Roland, I've only just discovered disParity and I think it's brilliant in it's ease of use! I have a question/feature suggestion: I have 3 data drives and a soon to be parity drive. On the data drives I don't need all the folders to be in disParity. On my first drive I have the following folders: E: |>TV |>Movies |>Photos |>Documents I would like to use disparity to help protect photos and documents, but not the other two. Is that possible? rust0r on "Successful recover!" 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/ 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. 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. 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! romwarrior on "Not enough disk space error" 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/ I think this is a different issue than the other disk space thread, but if not you can delete this. 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." However, my parity disk is the biggest disk. Here is what Windows shows: Drive - Capacity - Free Space Media1 - 1397.26GB - 22.99GB Media2 - 1397.26GB - 60.34GB Media3 - 1397.26GB - 220.42GB Media4 - 1863.01GB - 202.76GB Media5 - 1863.01GB - 48.41GB Parity - 1863.01GB - 28.23GB Right now the file is on the Media4 drive but it was originally on the Media5 drive. 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. Klaatou on "Testing Failures" http://www.vilett.com/disParity/forum/topic.php?id=97#post-661 Tue, 20 Apr 2010 03:17:44 +0000 Klaatou 661@http://www.vilett.com/disParity/forum/ Hello ! I'm glad of my data reorganization, my disks are almost full and parity creation was OK , the 67MB log file ends with : "6,19 TB protected in 53 798,42s (120,65 MB/sec)" The Verify command gave me : "Verify complete. Errors: 0" Then I tried the testing feature on one of the disk and got some lines as this one : "Testing STE\STE-S1\_STE-S1-V6-par2...Verify FAILED!" With that at the end : "Tested 5785 files (903,24 GB) in 70222,98 sec. Failures: 64 Verify complete. Errors: 0" I don't understand why there is some failures and at the end 0 error. I tried then the HashCheck command and got the same kind of response. I did no modification to my data before or during the tests so I don't understand, what do you think of that ? I don't see the differences between all the commands "test, verify, HashCheck" and didn't found an answer in the forum, where can I find it please ? Thenk you ! Roland on "Registration problems" http://www.vilett.com/disParity/forum/topic.php?id=96#post-660 Mon, 19 Apr 2010 11:27:38 +0000 Roland 660@http://www.vilett.com/disParity/forum/ It just came to my attention that the "reCAPTCHA" system I was using to block spam registrations to this forum has stopped working. Or rather, it was working too well, in that it was rejecting every attempt to solve the CAPTCHA, even obviously correct ones. I Google'd around a bit to find a solution and came up empty handed. I don't have time to pursue this problem further right now so I've disabled the registration CAPTCHA. Hopefully we won't get flooded with a bunch of spam now. Klaatou on "Insufficient disk space available" http://www.vilett.com/disParity/forum/topic.php?id=86#post-538 Wed, 27 Jan 2010 07:49:59 +0000 Klaatou 538@http://www.vilett.com/disParity/forum/ Hello I think disParity is exactly what I was looking for to protect my movies and mp3 ;) I have 7 one tera disks and wanted to protect 6 of them on the 7th. they are all identical but I have this error trying to create the parity : Disk space required for parity: 933,55 GB Disk space available on P:\: 931,42 GB Insufficient disk space available. is it a way to use my disks or am I forced to have a bigger one ? thank you Cool1Net6 on "GUI: DisParity Storage Manager" http://www.vilett.com/disParity/forum/topic.php?id=57#post-269 Sun, 13 Sep 2009 21:24:54 +0000 Cool1Net6 269@http://www.vilett.com/disParity/forum/ About a month ago I stumbled across this application when trying to find out more information on FlexRAID. What intrigued me about it is that it works exactly like FlexRAID, but I could actually understand how it works and use it quite easily. Scanning this forum, I also discovered that a GUI was being requested, and Roland himself was unavailable for the job. Tada! I see a weekend project! After heavily coding for one weekend (hours on end), I was able to get a functioning prototype GUI that contained the three core functions (create, update, restore) and gave information on the drives status. Since then I updated the app to automate all of disParity's functions and a few optimizations here and there, and a month later (to the day) I want to present what I have developed so far. I call it the "DisParity Storage Manager". Although this is a working copy, it hasn't met my quality bar and I do not want to release it, however, here are a few screen shots of progress. <a href="http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Main.png" rel="nofollow">http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Main.png</a> <a href="http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Menu.png" rel="nofollow">http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Menu.png</a> <a href="http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Building.png" rel="nofollow">http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Building.png</a> <a href="http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Finished.png" rel="nofollow">http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Finished.png</a> <a href="http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Remove.png" rel="nofollow">http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Remove.png</a> <a href="http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Broken.png" rel="nofollow">http://i64.photobucket.com/albums/h176/StepForwarD/DSP_Broken.png</a> Its going to take me a while to really perfect this application as work just got more intense and I have less time to focus my effort here, but if you like what you see or if anyone is even still interested in the development of a GUI, just reply to this thread. I will check on it every now and then. Thanks. -Cool- rust0r on "Parity drive takes up more space than any other drive?" http://www.vilett.com/disParity/forum/topic.php?id=95#post-650 Tue, 23 Mar 2010 18:01:38 +0000 rust0r 650@http://www.vilett.com/disParity/forum/ I don't think this has been covered before (at least I wasn't able to find it), this has occurred under both 0.16 and 0.21, so it isn't limited to the newest version. I'm running 5 data drives and 1 party (all identical 1tb WD Blacks) Having recreated my parity, it sits at 134GB FREE, the fullest data drive is showing 137GB FREE (thus there is more information on my parity drive, than the fullest of my data drives). My understanding is this shouldn't be able to happen at all, if things were REVERSED it could be attributed say to hidden files, however I am having the opposite problem in this case. Any ideas? Roland on "Version 0.21 available" http://www.vilett.com/disParity/forum/topic.php?id=94#post-642 Sat, 27 Feb 2010 10:02:35 +0000 Roland 642@http://www.vilett.com/disParity/forum/ Version 0.21 of disParity is now available for download: <a href="http://www.vilett.com/disParity/disParity0.21.zip" rel="nofollow">http://www.vilett.com/disParity/disParity0.21.zip</a> Changes in 0.21: <ul> <li>Fixed a bug introduced in 0.20 where moved or renamed files would also be removed completely from parity, and then added back on the next update.</li> </ul> rust0r on "Added 500GB of files, not all files are actually being added, some even removed?" http://www.vilett.com/disParity/forum/topic.php?id=93#post-604 Sun, 14 Feb 2010 12:32:58 +0000 rust0r 604@http://www.vilett.com/disParity/forum/ First off, I just want to thank you Rolland. My good friend Neostim has been trying to get me to make the switch from my RAID5 setup over to disparity for quite some time now. I recently built a home file server for all of my data (mostly movies, bluray, tv shows, etc, about 6TB currently and soon to expand). For my server I had attempted numerous setups with RAID (freenas, ubuntu, etc), all of which were frustrating and proved error prone when simulating fails/recoveries. Disparity is by far much easier/reassuring in event of failure/recovery! I apologize for the topic title, I really was not sure how to describe it in such few words. My question related to a problem I am having with the addition of new files. All of my drives are 1TB, including the parity drive. From my understanding the parity drive is suppose to be the same size as the fullest drive (in terms of space used). Everything was completely fine, my parity drive had 204GB free, and my fullest drive also had 204GB free. I added approx 500GB of files (mostly TV shows, large files) and renamed some of my old TV shows, this meant that my fullest drive now had 92.5GB free out of a possible 931 (1TB). I then ran the update, it added my new files, and "moved" the renamed files. The weird thing was that after it was all said and done, there still about 100GB+ difference between the fullest drive (my tv shows) and the parity drive. I looked in the log file (which I can email if need be) and noticed that the files I had renamed had been "moved" and then later "removed". As a result I ran the update for a second time, at this point it ADDED all of the previous files in which it "removed" (which were always physically present on the drive). To give you an idea, between both updates, no files were added/deleted off the drives. After the 2nd update completed, it told me it added 200 GB to parity, my parity drive now appears to have 100GB free, while my fullest drive only has 92.5GB free. I am tempted to just format the parity drive and run "create" again, but wanted to get your input on this and see if it is something you have encountered before. Thanks again, Tony evilx on "Change where disParity writes temp files?" http://www.vilett.com/disParity/forum/topic.php?id=92#post-593 Sat, 06 Feb 2010 06:50:25 +0000 evilx 593@http://www.vilett.com/disParity/forum/ Roland, is there an easy way to change where disParity writes the .tmp files it uses while processing large files? Using WHS I only have about 8GB free on the system drive (only 20GB partition... why MS, why?) but some of my files are on the order of 12GB+ and they get skipped during an update because the temp file can't be written. The only thing I'm thinking is "installing" disParity on the D: drive (~200GB free) but maybe in a future release could you add an option in the config file? I know you wanted to keep options to a minimum, but that one seems like a simple one to me. Thanks. dldummy on "System.IO.FileSystemWatcher" http://www.vilett.com/disParity/forum/topic.php?id=91#post-586 Mon, 01 Feb 2010 16:18:47 +0000 dldummy 586@http://www.vilett.com/disParity/forum/ Hi Roland .. At weekend i was a little bit curious ... so i taked a look into Source of Disparity ... >Monitor.cs ... As i see ... you experiment with System.IO.FileSystemWatcher How does your experiemnts go !? Somewhere in the past i experimented .. not with NET but with WMI-EventSinks, there is one Eventsink for Filechanges ... (fine is .. you can watch changes on another machine) Its another API but i think it use the same feature of windows ... My results where, if i remember right, that my Eventhandling (only VBA) was to slow ... If i copied a small amount of files it worked ... But Moving/copying 100 ore more files, resulted in massive loss of changes .... I now overvied MSDN ... There is an internalBuffer for the events .. it can overflow and this result in loss of events ... an OnError is then raised ... and you can set the BufferSize in 4K steps but it use NonPagedMemory (its not swapped) so its better to keep it as small as possible. I dont now of which Stadium (how old) the codefragments in v0.2 are but i missed the capturing if errors (BufferOverflow) and IncludeSubdirectories isnt set. The handling of events is TimeCritical ... how do you plan to implement ... Write changes to log .. and make parity asynchron by another thread, activated by PerfCounter/CpuUsage ore somthing simmilar ? And how can we be shure that we dont miss events ... or to be exact ... what to do if Bufferoverflow occures ... We know that we loosed filechanges but not for which files ? So we need manual scan ... so its not LIVE ... How much live do you think should live be ? I have the feeling that safe Real-Live can only be done by Hooks to filesystem like Rootkits or AV-Software do. And if live means real live ... we need VolumeShadowCopy ... But VolumeShadowCopy of 6 ore more drives at same time .... hmmmm !? And for me and some others then it start to be complicated ... I dont know how VolumeShadowCopy works wit As FolderMountedVolumes and CrossDisk hardlinks ... ! I wrote some posts before that i dont need the Life Feature ... but that dont mean that its not worth to think about ways, how it can be realized ... joebanana on "Keeps adding stuff" http://www.vilett.com/disParity/forum/topic.php?id=90#post-582 Sun, 31 Jan 2010 15:45:22 +0000 joebanana 582@http://www.vilett.com/disParity/forum/ First off, great great tool. Simple, light, easy, just what I needed. Question now. Everytime I run the update, it seems the tool keeps adding files that are present already, and were not altered. Scanning H:\... Adds: 2 Moves: 0 Deletes: 0 Loading file data for I:\...2685 records loaded. Scanning I:\... Adds: 0 Moves: 0 Deletes: 0 Loading file data for J:\...2550 records loaded. Scanning J:\... Adds: 0 Moves: 0 Deletes: 0 Loading file data for K:\...792 records loaded. Scanning K:\... Adds: 0 Moves: 0 Deletes: 0 Processing adds... Disk space available on P:\: 1.35 GB Adding H:\Backdrops\Music\Jason Mraz.jpg... Adding H:\Backdrops\Music\Jay-Z.jpg... 2 files (380.34 KB) added in 0.72 sec Here is the latest example. I just had run an update and ran it once again right after to see what it would add again. This time I got lucky it only added two, but why? I ran the 2nd update right after the 1st... Any idea? dldummy on "Calculation Example - Parity Space needed" http://www.vilett.com/disParity/forum/topic.php?id=89#post-566 Fri, 29 Jan 2010 04:07:39 +0000 dldummy 566@http://www.vilett.com/disParity/forum/ A SIMPLE calculation ... to clarify the extraspace neede for parity In this example it dont care about the extra space needed to store by File system (FileSystem management, Blocksize of Filesystem,...) And i know tyhat 1 KB is 1024 Byte and not 1000 ... but its simpler to calculate, and it dont mather for this example. 1 TB = 1000 GB = 1 000 000 MB = 1 000 000 000 KB = 1 000 000 000 000 B disParity split the files in blocks to xor them together. So if the filesize isnt a exact multiplie of the Blocksize you have to add a whole block extra. In worst case you nedd a whole block for only 1 Byte more ... the rest is filld up with 0. I dont count the extra space neede by disparity to manage parity (Store Filename,Path,Date/Time,Blocknumbers,.....) Becous there is no way i can calculate that, it depends on FilenameLength, Pathlength, how the informations are stored (FixLength Fields or not) ... So i ignore it and say you need a little bit more than the calculated value I dont know the bloksize disparity use but for my example, i use a blocksize of 512 KB (512000B) Our experiment take the worst case that every file is 1 bytes bigger than the multiple of the Blocksize so you need 512KB mor than the filesize for parity, for each file. And we make parity for only one 1TB drive ... in real that would be senseless, but so its easier to calculate, and if you have more drives it dont change so much on the way it works. the worst case is the simplest. You have files with only 1 Byte length ... Files: 1 000 000 000 000 ParitySize: 512 000 000 000 000 000 Byte (512 000 TB) Yes that is so much you need 1 Block (512KB) for each of the files ... I know that its impossible to do this in real, its only an example of calculation. If you have 1 TB DATA full of MP3 or Pictures each 4 MB Files: 250 000 ParitySize: 1 128 000 000 000 Byte (1TB 128GB) If you fill the drive wit 1CD Video-RIPs ... i calculate with 700MB Files: 1428 ParitySize: rounded 1 000 731 000 000 Byte (1TB 731MB) If you have untouched Rips of your Blurays each on is a 25GB ISO Files: 40 ParitySize: rounded 1 000 020 000 000 Bytes (1TB 20MB) If the Blocksize used by disparity is smaller i calculated in this example, you need less, if bigger you need more extraspace. And as told at beginning there is more ManagementData to store and so the needed size is bigger as here calculated. And in real life its a little more complex becous you have more then 1 data Drive and miexd filesizes. But this example can help to get a feeling how the Filesize affects the needed Paritysize. Or is my calculation completly wrong ....? What do you think Roland ? dldummy on "Suggestions - Simulate Command, Output Format" http://www.vilett.com/disParity/forum/topic.php?id=87#post-539 Wed, 27 Jan 2010 09:01:07 +0000 dldummy 539@http://www.vilett.com/disParity/forum/ Hi Roland, its me again .... I did some Brainstorming (with me) about disparity ... and have some Suggestions / Whishes / Questions : NEW - Command SIMULATE It would be useful if there is a Command like SIMULATE Now, the only Chanche to see if there is a need for Update is to do it ... What should SIMULATE do !? the same as UPDATE but without doing it ... Dont Calculate XOR and DONT modify PARITY But it lists every modified, moved, deleted File and lists at end OldParitySIze, NewParitySize, moved,modified,deleted Filecount and Filesize. NewParitySize in Bytes is needfull if want to be shure that ther is enoughe Parity Space ... The other resaon for SIMULATE is ... with it its possible for GUI to know if DATA/PARITY is dirty and inform/warn user that he needs to UPDATE ... MOD - OUTPUT FORMAT The Output of disParity is the only way to know what happen or happend ... But its not Structured, its not Machine reading optimized, and for Script or GUI its hard to read and interpret ... Its more like an Debug output ... for Human reading its OK, but in future, to build a full featered GUI its hard to interpret. Suggestions: TIMESTAMP [ACTION] INFORMATION <STATUS> 2010-01-27 16:30:01 [COMMAND] UPDATE <OK> 2010-01-27 16:30:01 [PREINFO] C:\DEVRAID\RAID001\ | DRU001 <OK> 2010-01-27 16:30:02 [RECORDS] 134 <OK> 2010-01-27 16:30:03 [ADDS] 1 | 13467 Bytes <OK> 2010-01-27 16:30:04 [MOVES] 0 | 0 Bytes <OK> 2010-01-27 16:30:05 [DELETES] 0 | 0 Bytes <OK> 2010-01-27 16:30:06 [PREINFO] C:\DEVRAID\RAID002\ | DRU002 <OK> 2010-01-27 16:30:07 [RECORDS] 345 <OK> 2010-01-27 16:30:08 [ADDS] 0 | 0 Bytes <OK> 2010-01-27 16:30:09 [MOVES] 0 | 0 Bytes <OK> 2010-01-27 16:30:10 [DELETES] 0 | 0 Bytes <OK> 2010-01-27 16:30:11 [PREINFO] C:\DEVRAID\RAID003\ | DRU003 <OK> 2010-01-27 16:30:12 [RECORDS] 567 <OK> 2010-01-27 16:30:13 [ADDS] 0 | 0 Bytes <OK> 2010-01-27 16:30:14 [MOVES] 0 | 0 Bytes <OK> 2010-01-27 16:30:15 [DELETES] 0 | 0 Bytes <OK> 2010-01-27 16:30:16 [PROCESS] C:\DEVRAID\RAID001\ | DRU001 <OK> The GUI can now initialize Progressbars ... Esteminate Time to complete .... or what else .... 2010-01-27 16:30:17 [ADD] F:\Mediafolder\Video\SomeFilm\Somefilm.avi <OK> 2010-01-27 16:30:18 [ADD] F:\Mediafolder\Video\SomeFilm\folder.jpg <HIDDEN-IGNORE> 2010-01-27 16:30:19 [PROCEND] C:\DEVRAID\RAID001\ | DRU001 <OK> 2010-01-27 16:30:20 [PROCESS] C:\DEVRAID\RAID002\ | DRU002 <OK> 2010-01-27 16:30:20 [PROCEND] C:\DEVRAID\RAID002\ | DRU002 <OK> 2010-01-27 16:30:21 [PROCESS] C:\DEVRAID\RAID003\ | DRU003 <OK> 2010-01-27 16:30:22 [PROCEND] C:\DEVRAID\RAID003\ | DRU003 <OK> 2010-01-27 16:30:23 [POSTINFO] EMPTY <OK> 2010-01-27 16:30:24 [SUMADDS] 1 | 13467 Bytes <OK> 2010-01-27 16:30:25 [SUMMOVES] 0 | 0 Bytes <OK> 2010-01-27 16:30:26 [SUMDELETES] 0 | 0 Bytes <OK> 2010-01-27 16:30:27 [SUMIGNORES] 1 | 3450 Bytes <OK> 2010-01-27 16:30:28 [SUMERRORS] 0 <OK> 2010-01-27 16:30:29 [SUMWARNINGS] 0 <OK> 2010-01-27 16:30:30 [SUMTIME] 22 Sec <OK> 2010-01-27 16:30:30 [END] EMPTY <OK> The DRUxxx thing is DataRiskUnit (i stole the name form FlexRaid ...) Why output DRUNumber!? Paths can Change but the DRUNumber (hopefully) stay the same. Hmmmm. a Qestion ... Can (Base)Paths change ? Do you store (in Parity) Absolut Paths or Relative to Path given by "dataX=" in config !? I tried to keep the order of the Current Log Output, so ther are only little Code changes needed ... Its only an quick Example to think / talk about .... If you are interested in reoranize the Output, i can think about it a little more and do a more complete list. What do other disParity Users think about it ? Specialy our GUI Builder klim ...