Help and Support
Ask a question, report a problem, request a feature...
<<  Back To Forum

Tixati doing FULL WRITES when allocating

by Guest on 2016/10/27 05:23:18 PM    
The only thing that has changed is that I swapped in a external FAT32 drive but Tixati NEVER did THAT.
It is explicitly overwriting my command to do a Sparse Allocation and it is infuriating! Last I used Tixati with this drive was 2.43 still.
Happening with both pre-existing transfer as well as new ones.
Can somebody please help me?

Tixati 2.47 / Windows 10 x64
by Guest on 2016/10/28 12:25:52 AM    
It is also unable to simply relocate the files, having to every single time do complete moves.
by Guest on 2016/10/28 04:10:33 AM    
FAT32 doe not SUPPORT sparse.
That is a limitation of the filesystem. You want sparse go to ntfs
by Guest on 2016/10/28 11:19:19 AM    
Thanks for the clarification but it still have to move every file? I'm sure it didn't do that before.
by Guest on 2016/10/28 11:29:00 PM    
For messages in "Event Log" for each transfer in your Tixati window... Fast move just "relinks" old location on one drive to NEW location on one drive.
WHENEVER you move to a different drive you will have to full copy. The problem is the data integrity Tixati ENSURES must be done for these operations. I experience this many times a day when I forget to move outside Tixati. Windows cacheing is superior to Tixati and moves at pretty much bus speed.
If these experiences you describe disappear when you (temporarily) stick in a NTFS formatted flash dongle just assume its because FAT32 is old and doesn't include things which are "standard" today.
If you want to get better performance you may even want to look at installing the EXT4 filesystem shim into your windows installation.

For "relocate" this option is used when your files do not match the information in the .torrent for your transfer.
"My_file.txt" instead of "myfile.txt" Relocate means you don't have the correctly named file.
Since I have found it much easier to do filesystem maintenance tasks outside Tixati I would suggest STOPPING the transfer in Tixati. Then renaming outside Tixati. Then Right click -> Force Recheck. The problem when using RENAME inside Tixati as follows: You are forced to merge, so it tries to deal with the data per-piece repetitively instead of what seems faster to me the "Force Recheck"

If i misunderstood your relocate problem please advise :D
by Guest on 2016/10/30 12:03:58 PM    
What I mean is, within Explorer, I can just cut and paste a file instantly but if I do it manually or through MoC in Tixati, it has to copy the files.
A waste of time, honestly.
It's just that since Windows can do it, why isn't Tixati doing it?
by Pete on 2016/10/31 01:31:22 AM    
See if the "Directly move file/folder if possible when changing location" option is enabled (Settings > Transfers > Files).
by Guest on 2016/11/03 11:26:40 AM    
I figured out what was going on.
Tixati thinks e:\downloads\unwanted and E:\downloads\unwanted are different drives thus it was doing a full move.
My default location was e:\ and then MoC'd to E:\.

Is this intended or is it a bug?
by Guest on 2016/11/03 08:47:10 PM    
Are you on Linux or Windoes? Windows is case IN-sensitive even though you can clobber the same name with different cases...

(BTW great find, did you confirm previous behaviour with both of them spelled the same?)
by Guest on 2016/11/05 02:00:10 AM    
I'm on Windows and yes, the destinations used where exactly the same outside the capitalized drive letters.




This web site is powered by Super Simple Server