Yesterday I was moving files from a network share to another location, when error messages started to pop up about some of the files and folders that were being moved, not being able to be read or written - apparently the names of these files and folders contained characters that are legal on the source file system (HFS+) but not the destination (ext4). The nasty part is that, even though the files/folders couldn't be read from the source volume or written to the destination volume, *the original files and folders were deleted anyway*. I lost piles and piles of important data, and while yes, I do keep backups, it's a terrific pain to sort through this mess and figure out which items need to be restored.
Clearly, if PCManFM can't read or write a file that it's been asked to move, it shouldn't delete it - either the unreadable file should be left alone, or the entire operation should be automatically cancelled when an error is encountered. Any plans to fix this catastrophic bug? Thanks very much for all the hard work you do on an otherwise great file manager!
Log in to post a comment.