tracker_query_storage fail, error no: 28, error info: No space left on device

简介: tracker_query_storage fail, error no: 28, error info: No space left on device

先说结论:

这个错误信息提示磁盘空间不足,导致tracker查询存储失败。错误代码28表示系统中没有足够的可用空间。这个问题的解决方法是清理磁盘空间,释放足够的存储空间。

[root@localhost fdfs]# fdfs_test /etc/fdfs/client.conf upload /home/1.txt 
This is FastDFS client test program v6.08
Copyright (C) 2008, Happy Fish / YuQing
FastDFS may be copied only under the terms of the GNU General
Public License V3, which may be found in the FastDFS source kit.
Please visit the FastDFS Home Page http://www.fastken.com/ 
for more detail.
[2023-05-12 14:43:58] DEBUG - base_path=/usr/local/fastdfs/client, connect_timeout=5, network_timeout=60, tracker_server_count=1, anti_steal_token=0, anti_steal_secret_key length=0, use_connection_pool=0, g_connection_pool_max_idle_time=3600s, use_storage_id=0, storage server id count: 0
[2023-05-12 14:43:58] ERROR - file: tracker_proto.c, line: 50, server: 192.168.11.134:22122, response status 28 != 0
[2023-05-12 14:43:58] ERROR - file: ../client/tracker_client.c, line: 1077, fdfs_recv_response fail, result: 28
[2023-05-12 14:43:58] ERROR - file: tracker_proto.c, line: 50, server: 192.168.11.134:22122, response status 28 != 0
[2023-05-12 14:43:58] ERROR - file: ../client/tracker_client.c, line: 899, fdfs_recv_response fail, result: 28
tracker_query_storage fail, error no: 28, error info: No space left on device

删除大文件在试试,停掉服务重启就可以了

可以通过以下步骤来清理磁盘空间:

  1. 查找大文件:使用命令行工具或图形界面工具,查找并删除占用大量磁盘空间的文件。可以使用“du”命令查找磁盘空间使用情况,然后删除不必要的文件。
  2. 清理临时文件:清理系统和应用程序生成的临时文件,这些文件通常存储在“/tmp”目录下。可以使用“rm”命令删除这些文件。
  3. 压缩文件:使用压缩工具(如tar、zip等)将不常用的文件压缩成一个文件,以节省磁盘空间。
  4. 删除不必要的软件包:删除不必要的软件包和文件,以释放磁盘空间。
  5. 扩展磁盘空间:如果以上方法无法释放足够的磁盘空间,可以考虑扩展磁盘空间,使用更大的硬盘或者在云服务器上扩展磁盘空间。

总之,清理磁盘空间是解决tracker_query_storage fail错误的最有效方法。在清理磁盘空间之后,需要重启tracker服务,以确保修改生效。

查看大文件  https://candy.blog.csdn.net/article/details/78982177

停掉服务 重启

fdfs_trackerd /etc/fdfs/tracker.conf  stop    
fdfs_storaged /etc/fdfs/storage.conf  stop  
fdfs_trackerd /etc/fdfs/tracker.conf  start    
fdfs_storaged /etc/fdfs/storage.conf  start

再次上传文件可以了。

fdfs_test /etc/fdfs/client.conf upload  /home/1.jpg

服务器磁盘空间不足,导致服务可以起来,但是文件传不上去。。。。。。

真是一步一坑啊。

目录
相关文章
|
3月前
|
XML C# 数据格式
The data at the root level is invalid. Line 1, position 1.
The data at the root level is invalid. Line 1, position 1.
22 0
|
3月前
|
Kubernetes 容器
【kubernetes】解决k8s1.28.4:"command failed" err="failed to parse kubelet flag: unknown flag: --c...
【kubernetes】解决k8s1.28.4:"command failed" err="failed to parse kubelet flag: unknown flag: --c...
271 0
|
4月前
DevTools failed to load source map: Could not load content for…System error: net::ERR_FILE_NOT_FOUN
DevTools failed to load source map: Could not load content for…System error: net::ERR_FILE_NOT_FOUN
|
8月前
|
前端开发 数据库
Failed to load response dataNo data found for resource with given identifier
Failed to load response dataNo data found for resource with given identifier
1049 0
|
应用服务中间件 nginx
[error] OpenEvent(“Global\ngx_reload_11812“) failed (2: The system cannot find the file specified
[error] OpenEvent(“Global\ngx_reload_11812“) failed (2: The system cannot find the file specified
|
Unix Linux 异构计算
成功解决 ERROR: An error occurred while performing the step: “Building kernel modules“. See /var/log/nv
成功解决 ERROR: An error occurred while performing the step: “Building kernel modules“. See /var/log/nv
成功解决 ERROR: An error occurred while performing the step: “Building kernel modules“. See  /var/log/nv
【问题】Log writing failed, No space left on device @ io_write - /mnt/project/log/development.log
【问题】Log writing failed, No space left on device @ io_write - /mnt/project/log/development.log
142 0
【问题】Log writing failed, No space left on device @ io_write - /mnt/project/log/development.log
SAP WM Storage Type Capacity Check Method 5 (Usage check based on SUT)
SAP WM Storage Type Capacity Check Method 5 (Usage check based on SUT)
SAP WM Storage Type Capacity Check Method 5 (Usage check based on SUT)
Whitelabel Error Page There was an unexpected error (type=Not Found, status=404). No message availab
Whitelabel Error Page There was an unexpected error (type=Not Found, status=404). No message availab
148 0

热门文章

最新文章