Home
JAQForum Ver 24.01
Log In or Join  
Active Topics
Local Time 06:59 02 Aug 2025 Privacy Policy
Jump to

Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.

Forum Index : Microcontroller and PC projects : LINUX: No such file or directory....

Author Message
Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9610
Posted: 06:25am 04 Oct 2021
Copy link to clipboard 
Print this post

Hi all.

I am getting this error with two files on an ext4 volume.
Linux insists that the file or directory does not exist, but it most certainly does.
I can get properties of the DIRECTORY that holds then, but trying to get the properties of either of these two files, generates the error.





I tried to rename the files, thinking that the question marks might be illegal or something in the Linux filesystem, but I just get the same error, so can't rename them either.

Any thoughts from the Linux users of the forum?

EDIT: Oh, BTW - have already run a full f2fsck on this volume, no errors to report with the filesystem itself.

Windows sees the files with Chinese characters in the filename - which is probably the issue(Linux does not like that), but I thought you'd be able to rename the files inside of Linux, even if the filename was illegal.  More to the point, I'm surprised that Linux would even ALLOW you to copy files to it, if the filename had illegal characters in it.......





I can certainly try renaming the files from inside Windows, but it would be nice to know of a way to do it inside of Linux, and not to have to rely on Windoze to change it - I only have one Windoze machine left, so would like to know a Linux method to get around this issue in the future.
Edited 2021-10-04 16:32 by Grogster
Smoke makes things work. When the smoke gets out, it stops!
 
Mixtel90

Guru

Joined: 05/10/2019
Location: United Kingdom
Posts: 7937
Posted: 06:43am 04 Oct 2021
Copy link to clipboard 
Print this post

Is this an NTFS volume by any chance? If it is then Windows will handle it with no problem but linux may struggle.
Mick

Zilog Inside! nascom.info for Nascom & Gemini
Preliminary MMBasic docs & my PCB designs
 
epsilon

Senior Member

Joined: 30/07/2020
Location: Belgium
Posts: 255
Posted: 08:04am 04 Oct 2021
Copy link to clipboard 
Print this post

Maybe it's a permission thing. You might have read access to the directory (so the files do show up), but not to the files themselves.
Can you open a Linux terminal, cd to the directory in questions and then do a 'ls -al' to see who owns the file and what kind of access other groups have?
Epsilon CMM2 projects
 
Rado
Regular Member

Joined: 27/11/2020
Location: Croatia
Posts: 59
Posted: 09:18am 04 Oct 2021
Copy link to clipboard 
Print this post

Linux these days in general does not have issues with Unicode characters, but the various file managers might have - in such case, an unrecognized Unicode character will often display a question mark as a replacement.
Have you tried to rename the files in Windows to something less Unicode-ish and see if that works?

Also, check how you mount the partition: if it was not mounted with UC-set in mind (iocharset=utf8) things like this might happen.

Renaming the file with NC might yield results on Linux. Might.
 
Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9610
Posted: 10:44am 04 Oct 2021
Copy link to clipboard 
Print this post

@ Mixtel90: No, it's ext4 on a Linux machine, mapped to the Windoze machine on the network.  But the actual volume is Linux ext4.

@ epsilon: Found the solution....

I cannot change the names via the NETWORK using Linux machine #2 to rename the problem files on Linux machine #1.

Screenshot from Linux machine #1:





Same two files, but this time the Chinese characters are replaced with boxes with numbers in them in the filename.  I can get the properties of these files on the LOCAL machine, and I can rename them fine - so I have.

A strange one, but easily fixable so long as I use the local Linux machine and not make the attempt via another Linux machine, SAMBA and the network.

EDIT: It is probably that SAMBA does not support non-English symbolic characters, correct?
Edited 2021-10-04 20:46 by Grogster
Smoke makes things work. When the smoke gets out, it stops!
 
Volhout
Guru

Joined: 05/03/2018
Location: Netherlands
Posts: 5091
Posted: 01:23pm 04 Oct 2021
Copy link to clipboard 
Print this post

Check this with the Puppy Linux forum. It may be caused by ROX (the file manager Puppy uses).

Volhout
PicomiteVGA PETSCII ROBOTS
 
Rado
Regular Member

Joined: 27/11/2020
Location: Croatia
Posts: 59
Posted: 01:41pm 04 Oct 2021
Copy link to clipboard 
Print this post

Samba is Unicode friendly and should easily display (and do anything with files) if a filename has Uc characters. However, that has to be enabled in smb.conf, and it will not work if you try to talk to older clients, as they do not know Unicode.
It looks to me that you have a machine somewhere where Uc support is not enabled.
 
scruss
Regular Member

Joined: 20/09/2021
Location: Canada
Posts: 91
Posted: 03:27pm 04 Oct 2021
Copy link to clipboard 
Print this post

  Volhout said  Check this with the Puppy Linux forum. It may be caused by ROX (the file manager Puppy uses).


Yes: Puppy is an extremely limited distribution, and makes some very poor decisions around i18n.
 
Grogster

Admin Group

Joined: 31/12/2012
Location: New Zealand
Posts: 9610
Posted: 11:22pm 04 Oct 2021
Copy link to clipboard 
Print this post

Acknowledged.  Thanks chums.
Smoke makes things work. When the smoke gets out, it stops!
 
Quazee137

Guru

Joined: 07/08/2016
Location: United States
Posts: 593
Posted: 04:24am 05 Oct 2021
Copy link to clipboard 
Print this post

It must be with puppy. On my old mint 18 I have music and video files from
Korea, Japan, China and Vietnam all in their native languages.

No problems accessing any of them across my network of Linux systems.
 
JohnS
Guru

Joined: 18/11/2011
Location: United Kingdom
Posts: 4044
Posted: 02:12pm 05 Oct 2021
Copy link to clipboard 
Print this post

Looks like part of the initial confusion was that the file name does not include any "?" (question mark) chars, although some tool(s) show the (weird, unicode) chars that way.

Good to see overall it got fixed!

John
 
Print this page


To reply to this topic, you need to log in.

The Back Shed's forum code is written, and hosted, in Australia.
© JAQ Software 2025