Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2026 Poal.co

239

Side note: I mainly use Nemo File Manager on Linux Mint, but with Windows File Explorer, I made these observations.

  1. Windows Explorer sometimes refuses to copy .zip files to a MTP device, but then it works when changing or removing the file extension.
  2. Copying or moving files from a MTP source causes the last file to reserve as much space storage as all selected files in the source. That amount is not written, but the file appears at that size in Windows Explorer, meaning that the file system is manipulated to reserve this amount of storage for tge file.

Problem: If, for example, I want to copy 100 files with 1 GB each, the target needs 199 GB free storage, because the last file (99 to 100 GB) temporarily reserves 100 GB. Not sure why it is done that way.

In addition, when moving from a source device that is a mass storage device, each file will be moved and deleted individually. For FTP, I havr not tested it yet. But for MTP source devices, first all files will be transferred, and then deleted from source. But if the transfer is cancelled, no files are deleted from the source.

^(Side note: I mainly use Nemo File Manager on Linux Mint, but with Windows File Explorer, I made these observations.) ---- 1. Windows Explorer sometimes refuses to copy `.zip` files to a MTP device, but then it works when changing or removing the file extension. 2. Copying or moving files from a MTP source causes the **last file** to reserve as much space storage as all selected files in the source. That amount is not written, but the file appears at that size in Windows Explorer, meaning that the file system is manipulated to reserve this amount of storage for tge file. Problem: If, for example, I want to copy 100 files with 1 GB each, the target needs 199 GB free storage, because the last file (99 to 100 GB) temporarily reserves 100 GB. Not sure why it is done that way. In addition, when moving from a source device that is a mass storage device, each file will be moved and deleted individually. For FTP, I havr not tested it yet. But for MTP source devices, first all files will be transferred, and then deleted from source. But if the transfer is cancelled, no files are deleted from the source.

(post is archived)

[–] • 1 pt (edited )

MTP is a shitfest on any platform, I remember someone reimplementing MTP on linux because the default option was unusable.

[–] • 0 pt

MTP indeed is only suitable for low amounts of files. Beyond that, it becomes unpredictably unstable. Also, MTP lacks parallelism and might decide to freeze / hang up randomly.

Directories load much faster in MTP with disabled thumbnails (Windows: List or Detail view instead of miniature/whichever shows preview thumbnails).