NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Backup fails because there is a period (".") at the end of my filename.
Hi, I'm trying to setup a backup on my new ReadyNAS 212 (Firmware 6.7.5). Whenever I run the backup I receive an error : Cannot read file 'opti/makeinclude/shared.mk.' (error: No such file or d...
You could of course use a different backup protocol (NFS or RSYNC).
Hello Phil140,
I used 2 different computers, Win10 and Win7, I was able to create a file with a "." in the end of the file name. I think you should not do it on Linux as Linux may read the word after the "." as filename extension.
Regards,
Thanks JennC.
I have a suspicion that Windows is playing a trick on you. What you see on file explorer window is, in reality, named "testfile.she..txt" on disk.
You might need to use the option on windows explorer to display the file type.
When I refer to a "filename" I am implying the filename+filetype. (Sorry for the confusion.)
:smileyhappy:
Hello Phil140,
The file that has "." also shows on the admin page when browsing the share that was set as destination on the backup job.
I also enabled HTTP access for that share and it also shows there.
Regards,
Hi JennC,
I'm sorry. I'm not really able to understand the confusion.
I did another test. This is what I did...1) From windows, I created a file "testfile..she" with no period at the end, but two periods in the middle.
2) From linux, in the same directory, I generated a file that has a period on the end of the filename (ie. after the '.she').touch testfile.she.
Then I waited for the incremental backup to run.
Then I went to the ReadyNAS and accessed it via telnet, and looked at the backup folder.This is what I found:
$ ls -al | grep testfile -rwxr-xr-x+ 1 root root 0 Jul 13 18:18 testfile.she..txt $
As you can see, the file "testfile.she..txt" is there as expected. That works.
However, the file "testfile.she." is not there. That is not good.
I don't see any errors in the log file this time, perhaps because it was an incremental backup.
For now, I won't be concerned about it. But it is a bit alarming that some of my files are not being backed up.
Thanks for your help. Maybe it's a problem with CIFS and netgear is unable to do anything about it.
If that is the case, I understand.
:smileyhappy:
Phil140 wrote:
Thanks for your help. Maybe it's a problem with CIFS and netgear is unable to do anything about it.
If that is the case, I understand.As far as Windows is concerned, it's an illegal file name.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx
- Do not end a file or directory name with a space or a period. Although the underlying file system may support such names, the Windows shell and user interface does not. However, it is acceptable to specify a period as the first character of a name. For example, ".temp".
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
