Console - File Browser list does not display files containing Chinese characters.
Describe the bug Files containing Chinese characters are not displayed in the console file explorer list, even though multiple paths exist within the bucket. Files with Chinese names in other paths display correctly. The current RustFS version is the latest mirror: 2025-10-28T07:26:[email protected]
To Reproduce
Steps to reproduce the behavior: No specific steps to reproduce.
Expected behavior
Abnormal file access in the console.
Screenshots
- The file browser in the console is not displaying a complete list of files, and does not contain Chinese characters:
Desktop (please complete the following information):
- OS: Windows 11
- Browser [e.g]
- Version [e.g. Version 141.0.3537.99 (Official Release) (64-bit)]
Additional context Docker containerized deployment, Linux version x86 Ubuntu 22.04
Got it, we are confirming
@MosonHe Sorry, I did not reproduce the problem you described. Please help me confirm the following.
- Open the browser console and check if the file list is returned correctly in the network interface.
- If not, please describe how you uploaded the file.
@cxymds Thank you very much for your hard work.
1.The front-end request URL for this file directory is:
http://IP:9001/zlzx-pm-bucket/?delimiter=%2F&list-type=2&max-keys=25&prefix=project%2Ff3eaf74c-a191-485e-8500-ac07f2d8a845%2Finfo_ledgers%2F
The response is as follows: there are no obvious errors, but the response message does not include files with names in Chinese characters:
<?xml version="1.0" encoding="UTF-8"?><ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Contents><ETag>"4151b89294151d8239e2ad698cc0325c"</ETag><Key>project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/E694BFE58AA1E58CBAE59D97E993B_ICnIYIv.xlsx</Key><LastModified>2025-10-22T13:17:46.880Z</LastModified><Size>1939516</Size></Contents><Contents><ETag>"4151b89294151d8239e2ad698cc0325c"</ETag><Key>project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/E694BFE58AA1E58CBAE59D97E993B_QKFTv6r.xlsx</Key><LastModified>2025-10-22T13:18:40.174Z</LastModified><Size>1939516</Size></Contents><Contents><ETag>"95e8ed5e701beee8206da6cf829b4fee"</ETag><Key>project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/output_0147e8e3.xlsx</Key><LastModified>2025-10-23T04:10:44.787Z</LastModified><Size>1934181</Size></Contents><Contents><ETag>"918266532e0932c723634a3685974bd6"</ETag><Key>project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/output_186e0315.xlsx</Key><LastModified>2025-10-23T05:24:23.080Z</LastModified><Size>1934136</Size></Contents><Contents><ETag>"89cadf740790d810c3a1971e28ac4c9a"</ETag><Key>project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/output_94fb1374_94fb1374_94fb1374.xlsx</Key><LastModified>2025-10-29T03:42:11.992Z</LastModified><Size>1934801</Size></Contents><Contents><ETag>"d727c60866ac6f49896ad8a0a6cec8e9"</ETag><Key>project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/output_b20a4edd.xlsx</Key><LastModified>2025-10-23T04:30:35.024Z</LastModified><Size>1935022</Size></Contents><Contents><ETag>"7a418fd808398525a705f6ec414be529"</ETag><Key>project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/output_db01c69b.xlsx</Key><LastModified>2025-10-23T04:41:45.704Z</LastModified><Size>1934132</Size></Contents><Contents><ETag>"ea032e03ffa796e44537d96174fcc61e"</ETag><Key>project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/output_ebc871cb.xlsx</Key><LastModified>2025-10-23T07:26:53.484Z</LastModified><Size>1933912</Size></Contents><Delimiter>/</Delimiter><IsTruncated>false</IsTruncated><KeyCount>8</KeyCount><MaxKeys>25</MaxKeys><Name>zlzx-pm-bucket</Name><Prefix>project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/</Prefix></ListBucketResult>
2.Regarding the method of file upload, I am developing a project management system using Django REST framework. In this system, files are uploaded to the backend via callbacks from the OnlyOffice online document editor. In fact, the file upload is handled by storages.backends.s3boto3.S3Boto3Storage. However, I don't think the upload method is related, because in this path, even if I upload files with Chinese characters directly from the console, they cannot be displayed, whereas files with names containing only English letters and numbers display correctly.
Thank you for providing the information. This is crucial for locating this bug, and we will pay attention to and resolve this issue.
Thank you for providing the information. This is crucial for locating this bug, and we will pay attention to and resolve this issue.
Hi @cxymds ,
Have you reproduced this bug on your end?
Hey @MosonHe ,
I was unable to reproduce this problem.
We have not received any follow-up response and are unable to reproduce this bug. Please upgrade to alpha.68 and test again. We will close this issue. If you still need a solution, please contact us and we will reopen the issue. Our email address is: [email protected]
https://github.com/rustfs/rustfs/releases/tag/1.0.0-alpha.68
We have not received any follow-up response and are unable to reproduce this bug. Please upgrade to alpha.68 and test again. We will close this issue. If you still need a solution, please contact us and we will reopen the issue. Our email address is: [email protected]
https://github.com/rustfs/rustfs/releases/tag/1.0.0-alpha.68
@loverustfs @cxymds Hi, everybody. I just upgraded to alpha. 76 version, this problem still exists. However, I have some new findings. If you check' Show Deleted Objects' on the console, these files with Chinese character file names will be displayed on the front end, and these files have sizes. The size of the files that are actually deleted will be displayed as 0. If you need me to provide more information, please let me know.
We have not received any follow-up response and are unable to reproduce this bug. Please upgrade to alpha.68 and test again. We will close this issue. If you still need a solution, please contact us and we will reopen the issue. Our email address is: [email protected] https://github.com/rustfs/rustfs/releases/tag/1.0.0-alpha.68
@loverustfs @cxymds Hi, everybody. I just upgraded to alpha. 76 version, this problem still exists. However, I have some new findings. If you check' Show Deleted Objects' on the console, these files with Chinese character file names will be displayed on the front end, and these files have sizes. The size of the files that are actually deleted will be displayed as 0. If you need me to provide more information, please let me know.
![]()
Ok,i reopened.
Hey @cxymds ,
Is this logic correct?
Hey @cxymds ,
Is this logic correct?
The size of the deleted file will be 0, because essentially deleting a file will be adding a new deleted version, which has no size
We have decided to make some adjustments regarding the deletion after opening the version, which may take some time as it involves object lists, deletion tags, versions, and other related content. We will make everything more reasonable. such as deleted files cannot be deleted again.
We have decided to make some adjustments regarding the deletion after opening the version, which may take some time as it involves object lists, deletion tags, versions, and other related content. We will make everything more reasonable. such as deleted files cannot be deleted again.
OK, there is only one folder in my rustfs bucket. Files with Chinese characters in file names cannot be displayed normally on the console page. I did turn on version control in alpha.6x, but only tested and deleted a small number of files, and then closed them. However, fortunately, these files actually exist under the server's directory, so they do not affect the use. Thank you for your hard work.
We have decided to make some adjustments regarding the deletion after opening the version, which may take some time as it involves object lists, deletion tags, versions, and other related content. We will make everything more reasonable. such as deleted files cannot be deleted again.
OK, there is only one folder in my
rustfsbucket. Files with Chinese characters in file names cannot be displayed normally on the console page. I did turn on version control inalpha.6x, but only tested and deleted a small number of files, and then closed them. However, fortunately, these files actually exist under the server's directory, so they do not affect the use. Thank you for your hard work.
It is recommended to upgrade to the latest version.
@cxymds @loverustfs 嗨,朋友们,我又有了些新的发现。我再次描述一下问题现象:一开始我使用两台服务器(以下简称A和B),通过docker部署了两个alpha.66版本的rustfs服务。其中A主机的zlzx-pm-bucket/project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/下,带有中文字符的文件名在console页面不会展示,但是在服务器中,文件是存在的,通过S3接口也可以正常访问文件。我将主机A的rustfs升级到了最新的alpha.76版本,问题依然存在。后续我通过rclone、rustic等工具将主机A的桶文件备份到主机B的桶中,但主机B和主机A的故障现象一致。
昨天我将主机B桶中的历史文件全部删除,然后再次使用rclone A:bucket B:bucket,没有变化,但是我将主机B的rustfs从alpha.66版本升级到最新的alpha.76版本之后,在主机B的桶中,可以正常看到所有的文件了。
Hi, friends, I have some new discoveries. Let me describe the problem again: at first I used two servers (hereinafter referred to as A and B) and Two alpha.66 versions of the rustfs service deployed via docker. Under zlzx-pm-bucket/project/f3eaf74c-a191-485e-8500-ac07f2d8a845/info_ledgers/ of host A, the file name with Chinese characters will not be displayed on the console page, but the file exists in the server and can be accessed normally through S3 interface. I upgraded the rustfs of host A to the latest alpha.76 version, the problem still exists. Later, I backed up the bucket files of host A to the bucket of host B through rclone or rustic tools, but the failure phenomena of host B and host A are the same.
Yesterday I deleted all the history files in host B bucket, and then used rclone copy A:bucket B:bucket again. there was no change, but I changed the rustfs of host B from alpha. Upgrade version 66 to the latest alpha. After version 76, all files can be seen normally in the bucket of host B.
主机A的文件路径:
File path for host A:
主机B的文件路径:
File path for host B:
相同路径下通过rclone同步的文件在控制台展示的效果不一样,在主机B这一侧,看起来正常了。
Files synchronized through rclone under the same path have different effects on the console. On the side of host B, it looks normal.
It looks like a bug in the metadata.
We will fix each issue after it is discovered, and the fix will take effect in future versions. Therefore, it may not be compatible with previous versions, including uploaded files. You can try using the previous files again after updating the latest version. If the problem still exists, please report it again and we will continue to resolve it ,Thank you very much
