Changes in this update are listed in the release notes.
I strongly encourage all beta users to update to 0.34 as soon as possible.
Please visit the beta page to download version 0.34.
disParity » Announcements
Version 0.34 beta available
(27 posts)-
Posted 2 years ago #
-
that's ok, scan doesn't stop for long length paths but I didn't start the update needed as most of my files are too long path with drive bender, I will try with a folder subst.
EDIT : ok subst drives are not reconized, even importing a 0.21 config with it
I will try a network share folderPosted 2 years ago # -
I'm not quite sure what you mean by "subst drives."
Posted 2 years ago # -
I mean a folder becomming a disk letter by the DOS command SUBST :
>subst Y: D:\{long folder name}
then you try to use Y: instead of the folder name, but it is not viewed in disparity
I tryed to share the forlders and mount them as drives, disparity see them but I still have thousands of too long names ....
I continue to sort my files and will try again.
Posted 2 years ago # -
OK. I'm still not clear what you mean by "subst drives are not recognized". I just tried using the subst command to mount a folder as a driver letter, and I was able to scan that new drive from disParity without any trouble. Then I tried it with a folder that had a long path name in it, and that seemed to worked too.
Posted 2 years ago # -
it is strange as my subst drives are not in the windows list when I try to add a drive, I only see them in version 0.21.
I saw before that long path names are not stopping anymore the program but they are refused.
Posted 2 years ago # -
That is indeed strange. So if you hit "Add Drive..." and then navigate to the Computer node (or the French equivalent :)) under which normally all the drives are listed, your subst drives are not listed there? That is especially strange since that entire dialog is .NET's built-in folder browser dialog, not one I implemented, so you would think it wouldn't have any problems like that.
You could always try adding it manually by editing your Config.xml file, I suppose!
Posted 2 years ago # -
yes I find it strange too ... but don't worry about your code, it is the same in the MS file explorer .... I think it is a nice new "feature" of windows 8 ......
But there is a lot stranger : of course I tried to edit config.xml, but I have then no scan at all and I stay on a "nice" "0 bytes used 0 bytes free - Up to date" with that as logs :
05/01/2013 21:56:20 Scanning U:...
05/01/2013 21:56:20 Could not scan U:: Impossible de trouver une partie du chemin d'accès 'U:\'.
05/01/2013 21:56:20 Beginning Update
05/01/2013 21:56:20 Update complete.So it seems Windows 8 have a big problem with this old DOS command even if subst drives are very well seen in DOS windows.
(I keep trying to get shorter my paths to try again a scan)
Posted 2 years ago # -
Ah, interesting, somehow along the way I missed the fact that you are on Windows 8.
No Windows 8 machines here (yet) so I'll have to leave this one alone for now. It doesn't sound like this is an issue people would normally run into anyway.
Posted 2 years ago # -
I don't think I told you I was on win8, and I was far to think to have problem with subst on it ....
yes what I try to solve is not for a lot of people ;)
Posted 2 years ago # -
So I tried with a shared folders for each of my 10x2TB + 1x1TB disks keeping net path (not mapping on a disk letter). Of course it didn't helped for my too long path file names but I had to be away from the computer for some days and was in a harry, I left it working on that.
But after some days I had a bad grey window telling something like Disparity ygui has stopped and must be closed.
I have now a logs files close to 700mo starting with
10/01/2013 01:11:36 Scanning \\Cray2xm\O\...
10/01/2013 01:11:36 Scanning \\Cray2xm\1\...
10/01/2013 01:11:36 Scanning \\Cray2xm\2\...
10/01/2013 01:11:36 Scanning \\Cray2xm\3\...
10/01/2013 01:11:36 Scanning \\Cray2xm\4\...
10/01/2013 01:11:36 Scanning \\Cray2xm\5\...
10/01/2013 01:11:38 Scanning \\Cray2xm\6\...
10/01/2013 01:11:45 Scanning \\Cray2xm\7\...
10/01/2013 01:11:46 Scanning \\Cray2xm\8\...
10/01/2013 01:11:46 Scanning \\Cray2xm\9\...
10/01/2013 01:11:50 Scanning \\Cray2xm\a\...
and a lot of "10/01/2013 01:11:46 Warning: skipping file" (too long path)And nothing about the problem at the end :
12/01/2013 09:19:54 Reading \\Cray2xm\5\autorun.inf
12/01/2013 09:19:54 Reading \\Cray2xm\5\Donnees (J) - Raccourci.lnk
12/01/2013 09:19:54 Reading \\Cray2xm\5\JJJ.icoI watched the logs up for about an hour and saw only this kind of lines : "reading" on the different disks.
The array is about 20 TB, I think I'm not the only one with big datas, maybe I have too many little files with my 4TB mp3 and logs are too big ....?
Posted 2 years ago # -
I don't think the size of your array is an issue. Mine is 20TB as well (with about 12TB actually filled) and I don't have a problem.
What do you mean by "4TB mp3"? I remember you mentioned something before about having millions of mp3 files. That possibly could be an issue. When disParity scans a disk for changes it builds a table of every file on the disk so that it can figure out what's changed since last time. Each record in that table takes up a little bit of memory. Normally this isn't an issue but if you have literally millions of small files it's possible you simply ran out of memory during the scan.
I have some ideas about ways to reduce memory usage during a scan for this case but it's too complex a change to undertake during this beta.
Posted 2 years ago # -
I tried the 0.34 beta (the first I tried of the “new” versions), and I get
“Error removing [filename]: Object reference not set to an instance of an object.”
Expected behaviour / known issue?Have to admit that the parity drive is more or less full, but I removed a couple of gigs and retried.
(Can I make disparity rebuild without deleting all the parity*.dat files and start over? Like, just remove one and save the three days?)
Posted 2 years ago # -
Not expected behavior, no. Sounds like a bug. If there is a crash.txt file here:
C:\Users\[username]\AppData\Local\disParity\crash.txt
can you email it to me at rolandv@gmail.com? Also the disParity.log file too if you can. Thanks!
After that, can you restart disParity and try it again? I assume you imported your old config right before doing this update, and it's possible something about the import process is causing this.
The only way to rebuild from scratch is to press Reset first (which deletes all of the parity data) then followed by an Update. This shouldn't really be necessary unless you think your parity data has become heavily fragmented over time due to lots and lots of deletes.
Posted 2 years ago # -
Nothing such created on this run. No log, and no disParity directory (and no crash.txt in it).
Tried to fix up using 0.21, command disparity update -v. First it was running seemingly successful for quite some time (i.e. for many log entries), until:
Saving file data for z:\...
Fatal error encountered during update: The process cannot access the file 'o:\files1.dat.BAK' because it is being used by another process.
Stack trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.Delete(String path)
at Disparity.DataPath.SaveFileList()
at Disparity.Program.RemoveFileFromParity(DataPath d, FileRecord f)
at Disparity.Program.Update()
at Disparity.Program.Main(String[] args)Then a second attempt, got only a 3k log file before:
Saving file data for z:\...
Fatal error encountered during update: Cannot create a file when that file already exists.Stack trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.__Error.WinIOError()
at System.IO.File.Move(String sourceFileName, String destFileName)
at Disparity.DataPath.SaveFileList()
at Disparity.Program.RemoveFileFromParity(DataPath d, FileRecord f)
at Disparity.Program.Update()
at Disparity.Program.Main(String[] args)... should I have deleted a .bak file or something?
Posted 2 years ago # -
(Where does the new version write its logs?)
Posted 2 years ago # -
(C:\Users\[username]\AppData\Local\disParity\logs ;)
Posted 2 years ago # -
Not under XP ... nothing under %appdata%\local .
Posted 2 years ago # -
Ah...XP...let me see if I can remember. It's the default application data folder, which is different under different versions of the Windows OS. Under XP I think it should be something like this:
C:\Documents And Settings\[username]\Application Data\disParity
Porcus, those errors seem quite odd to me. Did you try to run version 0.21 when the new UI version was also running?
Posted 2 years ago # -
I should add that I have not tested the new UI version under XP. I don't have any working XP machines left here, but I might be able to resurrect one. I don't know of any reason why it shouldn't work, but it sounds like maybe it doesn't.
Posted 2 years ago #
Reply »
You must log in to post.