Not always.
What in the fully chronicled psychotic breakdown is happening here?
That error is saying youâre trying to move/rename the file to a name thatâs already being used. Canât do that on windows either.
That said, Iâve seen some weird issues with bulk file copies in Linux file explorers. Cli usually works better.
You really seem annoying based off of all those edits.
Is it an ntfs partition that you opened on Windows? I remember getting an error like that cause Windows does some weird permission things. Other than that I'd try with the command line or a different file manager to try and discover what the error is.
It is indeed NTFS. I use the same HDD between a Fedora and Win 11 dual-boot, then the single HDD is being used by Plex, so no matter if I'm logged into Fedora or Win 11, it'll mount and read the content. It's just acting REALLY weird right now. About half of the content got moved to the new folder, while the rest of them errors out.
Have you shut down Windows without going through proper restart?
Windows has this really nasty habit of leaving NTFS partitions "dirty" until the next reboot, and fixing them on the fly when it starts. Meanwhile, if Linux is trying to use those partitions it will run into inconsistencies that will cause all kinds of errors.
There's no easy fix for this, other than shutting down Windows properly and hoping it left everything in working order. You can try using ntfsfix on Linux before mounting the partition but it's anybody's guess if it will fix everything.
You can't use another file system because exFAT and FAT are even worse than NTFS, and that's all Windows supports natively.
You can try the other way around and mounting Linux ext4 partitions under Windows using WSL2. I know it can be done, I haven't tried and can't tell you what performance is like.
Thank you for a proper reply. That could in fact be the case. I booted into Windows and tried to move all my movies into the folder, and it worked without issues, so I'm not entirely sure what happened in Fedora, but oh well.
You were given a lot of proper responses despite your unhinged edit rantings
Nemo on Windows can read extfs partitions better than NTFS plays with Linux. It's more of a problem with proprietary file systems, not the open source file manager trying it's best to reverse engineer the protocol.
When I dual booted, I would just share the extfs partition because it worked the best on both systems, once the extfs driver for Windows was installed.
wow, you sperged out quite hard about such a simple problem, I'm glad you will be using windows from now on and won't be hanging around *nix related discussion platforms
Like seriously, this was 2 minutes of googling. You're trying to move files to a target that already contains that file name. Just nuke the target directory and retry, or use one of the methods mentioned in the above article.
The Lord booted into God's Operating System, Windows 11 PRO (notice Pro, please) and the movement of stolen goods were completed within seconds. Linux might be better to keep the opposite sex away, but Windows brings it all night. Oh yes.
Maybe it is problem with NTFS, a filesystem outdated by 20 years that is still the only option on Windows.
Maybe it is problem with permissions.
Maybe it is something else.
But I won't help you, because od your language.
You should switch back to windows, that would fix your problem.
Have you tried switching it on and off again.
Try shutdown now -r
could be a perm issue
Are you crossing a physical boundary?
If you have rw on dest but not src âMovesâ (copy=>delete) can look like this
All it takes is for a lone soldier deep in a nest to have r - -
Love that movie.
thanks for using Leebra!
go to feed...
People use Windows because it comes preinstalled when they buy their computers.
save