升级HBlock
更新时间 2025-09-29 17:49:34
最近更新时间: 2025-09-29 17:49:34
本节主要介绍升级HBlock命令。
./stor upgrade { --filename | -f } file [ --archfile PACKAGE &<1-n> ] [ --key VALUE ]
此命令用来升级HBlock。对于集群，只需要在一台服务器上执行升级即可。
升级过程中系统会做检查，如果不符合升级条件，可能会导致升级失败，升级失败的原因可以在执行升级操作的服务器上查看日志upgrade.log（日志路径：HBlock安装目录/logs/ops/upgrade.log）。建议升级之前对系统进行检查，确保：
所有状态正常：
所有HBlock服务器连接正常，没有处于删除状态的服务器。
HBlock处于working、upgrading状态。
软件许可证证书在有效期内，且本地卷总容量未超过许可证容量限制；或者试用期未结束。
如果卷是高可用类型，至少保证卷的主备连接正常。
没有处于失败或者任务进行中状态的卷。
系统整体数据冗余度不降级，正常数据百分比为100%。并且，可用故障域数量和健康数量大于所有卷的写入需求。
升级监听服务（stor:ua）正常。
协议解析服务（stor:ps）正常。
基础服务正常：元数据管理服务（stor:mdm）、日志服务（stor:ls）、协调服务（stor:cs）。
HBlock使用的磁盘不存在Error状态。
注意
执行升级HBlock前，确保每个服务器的HBlock安装路径对应的文件系统，存在至少1 GiB的可用空间。
参数
| 参数 | 描述 |
|---|---|
| --filename file或-f file | 当前服务器升级的目标版本HBlock安装包具体路径和具体文件名称。 说明 当前服务器升级使用的安装包，必须保证与该服务器使用的安装包类型匹配。 注意 安装包的具体路径不要含有 -、--及空格。 |
| --archfile PACKAGE | 需升级的集群中其他不同架构服务器的安装包路径及文件名（仅集群版支持）。如果有多种不同类型服务器，应添加多个安装包，使用英文逗号隔开。 注意 当集群内存在与执行升级服务器架构不同的服务器时，才需指定此参数，用于指定相应架构服务器的HBlock安装包。 |
| --key VALUE | 升级至HBlock目标版本时，若该版本需导入参数，则须设置此项。具体参数设置应依据目标版本而定。若目标版本需多个参数，可多次按“--key VALUE”格式添加，其中“key”为参数名，“VALUE”为参数值。 |
升级
升级HBlock服务：从HBlock 3.9.2升级至HBlock 3.10.0。
[root@hblockserver CTYUN_HBlock_Plus_3.9.2_x64]# ./stor upgrade -f /mnt/storage01/CTYUN_HBlock_Plus_3.10.0_x64.zip
Starting upgrade, the current version is 3.9.2, the target version is 3.10.0
Start time: 2025-09-09 10:02:51
Server info:
hblock_1, 192.168.0.65, hblockserver
hblock_2, 192.168.0.64, k8s-master
hblock_3, 192.168.0.67, songt-0006
2025-09-09 10:02:51 CST+0800 [Step 1/5] Checking for system status...
2025-09-09 10:02:51 CST+0800 Checking system info
2025-09-09 10:02:51 CST+0800 Checking data status
2025-09-09 10:03:13 CST+0800 [Step 2/5] Uploading update files...
2025-09-09 10:03:15 CST+0800 Upload [100%] for hblock_1 ###[server 1/3]
2025-09-09 10:03:18 CST+0800 Upload [100%] for hblock_2 ###[server 2/3]
2025-09-09 10:03:20 CST+0800 Upload [100%] for hblock_3 ###[server 3/3]
2025-09-09 10:03:20 CST+0800 [Step 3/5] Upgrade preparing...
2025-09-09 10:03:40 CST+0800 [Step 4/5] Installing updates...
2025-09-09 10:03:40 CST+0800 Upgrading config - Update[√] ### [module 1/10]
2025-09-09 10:03:47 CST+0800 Upgrading storfsBase - Update[√] ### [module 2/10]
2025-09-09 10:03:55 CST+0800 Upgrading ls for hblock_1 - Check[√], Stop[√], Update[√], Start[√] ### [server 1/3] [module 3/10]
2025-09-09 10:05:15 CST+0800 Upgrading ls for hblock_2 - Check[√], Stop[√], Update[√], Start[√] ### [server 2/3] [module 3/10]
2025-09-09 10:06:05 CST+0800 Upgrading ls for hblock_3 - Check[√], Stop[√], Update[√], Start[√] ### [server 3/3] [module 3/10]
2025-09-09 10:07:24 CST+0800 Upgrading mdm for hblock_2 - Check[√], Stop[√], Update[√], Start[√] ### [server 1/3] [module 4/10]
2025-09-09 10:07:55 CST+0800 Upgrading mdm for hblock_1 - Check[√], Stop[√], Update[√], Start[√] ### [server 2/3] [module 4/10]
2025-09-09 10:08:26 CST+0800 Upgrading mdm for hblock_3 - Update[√] ### [server 3/3] [module 4/10]
2025-09-09 10:08:30 CST+0800 Upgrading ds-1 for hblock_1 - Check[√], Stop[√], Update[√], Start[√] ### [service 1/1] [server 1/3] [module 5/10]
2025-09-09 10:08:50 CST+0800 Upgrading ds-1 for hblock_2 - Check[√], Stop[√], Update[√], Start[√] ### [service 1/1] [server 2/3] [module 5/10]
2025-09-09 10:09:41 CST+0800 Upgrading ds-1 for hblock_3 - Check[√], Stop[√], Update[√], Start[√] ### [service 1/1] [server 3/3] [module 5/10]
2025-09-09 10:10:01 CST+0800 Upgrading ps for hblock_1 - Check[√], Stop[√], Update[√], Start[√] ### [server 1/3] [module 6/10]
2025-09-09 10:10:18 CST+0800 Upgrading ps for hblock_2 - Check[√], Stop[√], Update[√], Start[√] ### [server 2/3] [module 6/10]
2025-09-09 10:10:40 CST+0800 Upgrading ps for hblock_3 - Check[√], Stop[√], Update[√], Start[√] ### [server 3/3] [module 6/10]
2025-09-09 10:11:02 CST+0800 Upgrading tool - Update[√] ### [module 7/10]
2025-09-09 10:11:08 CST+0800 Upgrading remote for hblock_1 - Check[√], Stop[√], Update[√], Start[√] ### [server 1/3] [module 8/10]
2025-09-09 10:11:24 CST+0800 Upgrading remote for hblock_2 - Check[√], Stop[√], Update[√], Start[√] ### [server 2/3] [module 8/10]
2025-09-09 10:11:41 CST+0800 Upgrading remote for hblock_3 - Check[√], Stop[√], Update[√], Start[√] ### [server 3/3] [module 8/10]
2025-09-09 10:11:53 CST+0800 Upgrading monitor for hblock_1 - Check[√], Stop[√], Update[√], Start[√] ### [server 1/3] [module 9/10]
2025-09-09 10:12:09 CST+0800 Upgrading monitor for hblock_2 - Check[√], Stop[√], Update[√], Start[√] ### [server 2/3] [module 9/10]
2025-09-09 10:12:25 CST+0800 Upgrading monitor for hblock_3 - Check[√], Stop[√], Update[√], Start[√] ### [server 3/3] [module 9/10]
2025-09-09 10:12:41 CST+0800 Upgrading ws for hblock_1 - Check[√], Stop[√], Update[√], Start[√] ### [service 1/2] [server 1/3] [module 10/10]
2025-09-09 10:12:55 CST+0800 Upgrading ms for hblock_1 - Check[√], Stop[√], Update[√], Start[√] ### [service 2/2] [server 1/3] [module 10/10]
2025-09-09 10:13:10 CST+0800 Upgrading ws for hblock_2 - Check[√], Stop[√], Update[√], Start[√] ### [service 1/2] [server 2/3] [module 10/10]
2025-09-09 10:13:24 CST+0800 Upgrading ms for hblock_2 - Check[√], Stop[√], Update[√], Start[√] ### [service 2/2] [server 2/3] [module 10/10]
2025-09-09 10:13:40 CST+0800 Upgrading ws for hblock_3 - Check[√], Stop[√], Update[√], Start[√] ### [service 1/2] [server 3/3] [module 10/10]
2025-09-09 10:13:54 CST+0800 Upgrading ms for hblock_3 - Check[√], Stop[√], Update[√], Start[√] ### [service 2/2] [server 3/3] [module 10/10]
2025-09-09 10:14:16 CST+0800 [Step 5/5] Updating system info...
2025-09-09 10:14:17 CST+0800 [Post Upgrade] Cleaning...
2025-09-09 10:14:17 CST+0800 Cleaning hblock_1 ###[server 1/3]
2025-09-09 10:14:17 CST+0800 Cleaning hblock_3 ###[server 2/3]
2025-09-09 10:14:17 CST+0800 Cleaning hblock_2 ###[server 3/3]
2025-09-09 10:14:17 CST+0800 [Upgrade Complete] The system has been successfully upgraded to 3.10.0 version
