10-31-2014, 06:27 AM
Been using Vuze/Azureus for ages now, and I am very comfortable with the settings and configurations within the tool. My problem only started occurring within the last couple releases (maybe 5.2, maybe since 5.0 in fact). First the background/scenario involved.
I have Vuze setup to download to a particular directory (call it DL_Dir).
When the download is completed, I have it move to a staging folder where it continues to seed (call it Ready_Dir). This rule is set in the Options | Files | Completion Moving.
At some point in the future, I move it to a different location (call it Longterm_Dir) by right-clicking the completed Torrent, and selecting Advanced | Files | Move Data Files. Files in this location are always accessible, but Vuze will Start or Queue them based on seeding Auto Starting rules.
Everything works perfectly, and I have no problems with Vuze's performance or ability to handle these scenarios.
The unexpected behaviour I am experiencing is that as time goes on, Vuze will randomly (re-)create the directory structure for a previously completed (and moved) torrent in the Ready_Dir folder, but with no data files. Just directory structure, sometimes just root folder, sometimes deeper, but never quite the complete directory structure of the completed torrent. Not every seeding torrent in Longterm_Dir gets re-created, just a handful. This makes it annoying when I have to manually delete these folders, since I use my particular 3-folder sorting for various reasons.
Is this a bug? Is this the result of some configuration that I inadvertantly set?
Java 1.7.0_71 Oracle Corporation SWT v4233, win32 Windows 7 v6.1, x86 V5.4.0.0/4 az3
Windows 7 x64 Home Premium
I have Vuze setup to download to a particular directory (call it DL_Dir).
When the download is completed, I have it move to a staging folder where it continues to seed (call it Ready_Dir). This rule is set in the Options | Files | Completion Moving.
At some point in the future, I move it to a different location (call it Longterm_Dir) by right-clicking the completed Torrent, and selecting Advanced | Files | Move Data Files. Files in this location are always accessible, but Vuze will Start or Queue them based on seeding Auto Starting rules.
Everything works perfectly, and I have no problems with Vuze's performance or ability to handle these scenarios.
The unexpected behaviour I am experiencing is that as time goes on, Vuze will randomly (re-)create the directory structure for a previously completed (and moved) torrent in the Ready_Dir folder, but with no data files. Just directory structure, sometimes just root folder, sometimes deeper, but never quite the complete directory structure of the completed torrent. Not every seeding torrent in Longterm_Dir gets re-created, just a handful. This makes it annoying when I have to manually delete these folders, since I use my particular 3-folder sorting for various reasons.
Is this a bug? Is this the result of some configuration that I inadvertantly set?
Java 1.7.0_71 Oracle Corporation SWT v4233, win32 Windows 7 v6.1, x86 V5.4.0.0/4 az3
Windows 7 x64 Home Premium