Odd file error

[fohfoh]

So, like a true pirate, I grabbed some files off the web, and dled them to my computer. (Music actually) and lo and behold, after I finish dling them, I want them in another place instead of the default folder. So I (using vuze) choose advanced settings to move the data files.

Now, here's where things go wonky.

Sometimes, it only copies a folder and not the data files (Then pretends it worked like a good little software). Sometimes both data files AND folder are copied over. It's not really hard to cut and paste, but does anyone know what this issue stems from? If it was all the files I tried to move over... I would have assumed fault on my side for settings or something, but due to inconsistency, I have no idea how to even start looking up info about this error.

At first I thought the data files were lost, but going back in vuze and "launching" the torrent/checking to make sure data files exist (Which they still exist), I realized it was just copying a stupid folder over and not doing anything.

[billlanam]

Sometimes I have to go to the parent directory of destination dir. and click on the dest. dir. without going into it, in order to make it move the dir. and files correctly, its a problem with Vuze's selection handling. It works best when you are moving the files to an unrelated location, anotherwards not to a subdir. of your current dir. for example.

[daveLovesIt]

Yeah, basically any problems you get when running vuze is usually vuze itself. Before I switched to my current client, I tried a couple of versions of Vuze, and they both had bugs hiding around every corner. Too eager to get out a richly-featured and cross-platform client, not bothered enough about the rigorous design and polishing part. It's basically "bloat" and seems to be a common problem with many programs written in Java, often chosen as a solution to shortcut some of the effort involved to do just this.

It's a shame, because it has a really nice-looking interface, is spatially well laid-out and does just about everything a torrent client could be expected to. However, there was only so many times I could put up with my text files getting mangled when I hashed a new torrent, or variable names being echoed to the screen instead of the values they actually held... among other issues. I'm told that it has basically gotten worse since it became more commercial, but I've only really tried the "more commercial" strain. It's probably better supported on Windows than Linux, but not surprised to here it's quirky there too.

[Sosseres]

I've never had that problem. Are you running the files in some other program and that locks them?

[daveLovesIt]

No, I wasn't, AFAIK... still even if I was, I'd expect something as common as a lock-file conflict to be handled properly by such an all-singing all-dancing client. Now I think about it, and given the problems the windows users have with directories, I bet literally having a the torrent folder open could cause issues... or maybe it's my crappy old hardware not being supported sufficiently by Ubuntu or Vuze.

I had the worst problems (almost all of them actually) with the later version that I got from the website. The one in the repos was (mostly) fine, except it kept battering me with nags to update because my version was no longer supported; it wasn't a version conflict either, because I timed my upgrade with a full-system reinstall when I migrated from Ubuntu 9 to Ubuntu 10.

You running KDE or Gnome?

[fohfoh]

I'm on windows and no, don't think it's a file lock. Somehow the client thinks it has moved files over when in reality it hasn't and has only made a copy of the folder in the alternate location.

Oh well. I'm too lazy to bother. I'll just cut and paste it once it finishes seeding. Makes life "easier".

[daveLovesIt]

When copying a folder, any OS will first make the proper directory structure (this isn't a copy operation) then copy the files into it. Usual cause of empty dirs is not being able to read the source files or not being able to write to the new folder.

Try pausing the torrent (if you were still running it) and do the move command, then restart the torrent. Does this fix the issue? I don't know how windows handles copy vs move, but either windows or vuze is probably refusing to do the operation because of the files being in use. So this would be a lock issue. Perhaps you get the problem when someone is leeching from that folder only? Just a guess, tho.