Copy problem still exists

Questions about applications and software
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
freddyy
Level 1
Level 1
Posts: 5
Joined: Sat Aug 07, 2021 12:35 pm

Copy problem still exists

Post by freddyy »

Linux Mint 20.2 Uma



Copy problem still exists when copying a large folder (1.7 GB) with about
15 subfolders


The copy direction has the following influence:

Internal hard disk -> External USB hard disk without problems

External USB hard disk -> Internal hard disk -> error message invalid file name


The problem does not exist if the file names have no ":" and no "?" in the file names.

Knoppix 9.2 has no copy problem with ":" and "?" in the file names
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
Larry78723
Level 14
Level 14
Posts: 5476
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: Copy problem still exists

Post by Larry78723 »

What is the format of the external disc?
Image
If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject, it helps other users looking for help, and keeps the forum clean.
freddyy
Level 1
Level 1
Posts: 5
Joined: Sat Aug 07, 2021 12:35 pm

Re: Copy problem still exists

Post by freddyy »

Hello,

You can see the format in the attachment

Greeting
Attachments
Format_HDD.png
MAlfare

Re: Copy problem still exists

Post by MAlfare »

freddyy wrote: Thu Dec 02, 2021 4:15 pm
I don't believe that you can have filenames containing ":" or "?" in an NTFS file system..
If you should have, they are really invalid.
rene
Level 20
Level 20
Posts: 12212
Joined: Sun Mar 27, 2016 6:58 pm

Re: Copy problem still exists

Post by rene »

: and ? are although allowed as such on NTFS disallowed in names by Windows and the udisks2 automounter was tweaked so as to use the windows_names mount parameter to adhere to that as well; see viewtopic.php?p=2022654#p2022654

As said there, can not currently be easily undone other than by e.g. creating noauto /etc/fstab entries for the filesystems in question.
Locked

Return to “Software & Applications”