Timeline for Why filename with weird chars can be created but not accessed via CIFS?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 21, 2022 at 12:03 | comment | added | Marki555 |
Or you mean to backup the whole filesystem as one big zip archive? That won't work as I am running daily incremental backups via rdiff-backup tool.
|
|
| Nov 21, 2022 at 12:02 | comment | added | Marki555 | Also the 2nd is just workaround as it requires the files on the original fs to be removed/renamed and as those files are not mine, I don't want to do it unless really needed. But it might be useful for others, so I upvoted the answer. | |
| Nov 21, 2022 at 11:06 | comment | added | Prem | I updated that Answer , @Marki555 | |
| Nov 21, 2022 at 11:05 | history | edited | Prem | CC BY-SA 4.0 |
added 664 characters in body
|
| Nov 21, 2022 at 9:24 | comment | added | Marki555 | Yes, I could do that on the original filesystem, but there are at least 100 such files on this 300 GB filesystem and I'm not sure if customers are not referincing to those weird-encoded filenames from their database/websites. And I cannot rename it back to original, as the backup job to samba share will be run daily. | |
| Nov 21, 2022 at 5:19 | history | edited | Tom Yan | CC BY-SA 4.0 |
added 2 characters in body
|
| Nov 21, 2022 at 4:46 | history | answered | Prem | CC BY-SA 4.0 |