# 导入已存在的扇区数据

当我们希望将已经通过其他算力组件方案完成的扇区存储目录迁移到 venus-cluster 中时,只需要使用 venus-sector-manager 导入,并更新相应的配置文件即可。

# 导入及校验

注意:导入和校验都需要在未启动 venus-sector-manager daemon 的情况下进行。

# 导入

venus-sector-manager 提供了名为 storage attach 的导入工具,其使用方式如下:

venus-sector-manager util storage attach --verbose --name={storage name} <path>

其中:

  • name 是一个选填参数;
  • <path> 是存储路径,在导入过程中会被转换成绝对路径。

name<path> 的含义可以参考 Common.PersistStores (opens new window)

举例来说,我们使用

venus-sector-manager util storage attach --verbose --name=a -v ./mock-tmp/remote

通常会产生类似下面的日志:

2022-03-11T16:03:52.492+0800    DEBUG   policy  policy/const.go:18      NETWORK SETUP   {"name": "mainnet"}
2022-03-11T16:03:52.493+0800    INFO    cmd     internal/util_storage.go:104    use match pattern "/home/dtynn/proj/github.com/ipfs-force-community/venus-cluster/mock-tmp/remote/sealed/*"     {"name": "a", "strict": false, "read-only": false}
2022-03-11T16:03:52.493+0800    INFO    cmd     internal/util_storage.go:121    path "s-t010000-16" matched=true        {"name": "a", "strict": false, "read-only": false}
2022-03-11T16:03:52.494+0800    INFO    cmd     internal/util_storage.go:121    path "s-t010000-17" matched=true        {"name": "a", "strict": false, "read-only": false}
2022-03-11T16:03:52.494+0800    INFO    cmd     internal/util_storage.go:121    path "s-t010000-18" matched=true        {"name": "a", "strict": false, "read-only": false}
2022-03-11T16:03:52.508+0800    INFO    cmd     internal/util_storage.go:148    sector indexer updated for s-t010000-16 {"name": "a", "strict": false, "read-only": false}
2022-03-11T16:03:52.509+0800    INFO    cmd     internal/util_storage.go:148    sector indexer updated for s-t010000-17 {"name": "a", "strict": false, "read-only": false}
2022-03-11T16:03:52.509+0800    INFO    cmd     internal/util_storage.go:148    sector indexer updated for s-t010000-18 {"name": "a", "strict": false, "read-only": false}
2022-03-11T16:03:52.509+0800    INFO    cmd     internal/util_storage.go:152    3 sectors out of 3 files have been updated      {"name": "a", "strict": false, "read-only": false}
2022-03-11T16:03:52.509+0800    WARN    cmd     internal/util_storage.go:153    add the section below into the config file:     {"name": "a", "strict": false, "read-only": false}

[[Common.PersistStores]]
Name = "a"
Path = "/home/dtynn/proj/github.com/ipfs-force-community/venus-cluster/mock-tmp/remote"
Strict = false
ReadOnly = false

这时目录导入就已经完成了,所有扇区的位置信息也被记录了下来。 我们将最后输出的范例配置复制并填写到 venus-sector-manager 的配置文件中即可完成导入工作。

# 重新导入

如果我们发现导入时填写的信息有误,例如 --name 出现了拼写错误,那么我们只需要重新使用正确的信息完成一次导入流程即可。 扇区的位置信息会被覆盖更新。

# sealed_file 与 cache_dir 分离

一些算力组件允许 sealed_filecache_dir 位于不同的存储实例上,这种情况下,常规导入可能会无法正常定位扇区文件。 这种情况下,可以通过增加命令行参数 --allow-splitted 来启用分隔扫描模式,在这种模式下,会单独扫描 sealed 文件夹和 cache 文件夹中符合扇区命名规则的路径,并分别记录定位信息。

此时,日志会类似:

2022-04-19T19:11:55.137+0800    DEBUG   policy  policy/const.go:18      NETWORK SETUP   {"name": "mainnet"}
2022-04-19T19:11:55.154+0800    INFO    cmd     internal/util_storage.go:120    scan for sectors(upgrade=false) {"name": "p3", "strict": false, "read-only": false, "splitted": true}
2022-04-19T19:11:55.154+0800    INFO    cmd     internal/util_storage.go:211    0 sectors out of 0 files have been found        {"name": "p3", "strict": false, "read-only": false, "splitted": true}
2022-04-19T19:11:55.154+0800    INFO    cmd     internal/util_storage.go:145    scan for splitted cache dirs(upgrade=false)     {"name": "p3", "strict": false, "read-only": false, "splitted": true}
2022-04-19T19:11:55.155+0800    INFO    cmd     internal/util_storage.go:211    3 sectors out of 3 files have been found        {"name": "p3", "strict": false, "read-only": false, "splitted": true}
2022-04-19T19:11:55.156+0800    INFO    cmd     internal/util_storage.go:120    scan for sectors(upgrade=true)  {"name": "p3", "strict": false, "read-only": false, "splitted": true}
2022-04-19T19:11:55.156+0800    INFO    cmd     internal/util_storage.go:211    0 sectors out of 0 files have been found        {"name": "p3", "strict": false, "read-only": false, "splitted": true}
2022-04-19T19:11:55.156+0800    INFO    cmd     internal/util_storage.go:145    scan for splitted cache dirs(upgrade=true)      {"name": "p3", "strict": false, "read-only": false, "splitted": true}
2022-04-19T19:11:55.156+0800    INFO    cmd     internal/util_storage.go:211    0 sectors out of 0 files have been found        {"name": "p3", "strict": false, "read-only": false, "splitted": true}
2022-04-19T19:11:55.156+0800    WARN    cmd     internal/util_storage.go:166    add the section below into the config file:     {"name": "p3", "strict": false, "read-only": false, "splitted": true}

[[Common.PersistStores]]
Name = "p3"
Path = "/home/dtynn/proj/github.com/ipfs-force-community/venus-cluster/mock-tmp/pstore3"
Strict = false
ReadOnly = false

注意,使用这种模式需要确认:

  • 目标目录中不存在由于存储异常导致的重复存储的文件
  • 仅有 cache_dir 而无与之对应的 sealed_file 的扇区仍然无法正常定位

# 校验

venus-sector-manager 提供的 storage find 工具可以用来检查扇区导入的结果是否正确,其使用方式如下:

venus-sector-manager util storage find <miner actor id> <sector number>

继续以上面示范的导入工作为例,我们希望检验扇区 s-t010000-17 是否已被正确记录,可以使用:

venus-sector-manager util storage find 10000 17

通常会产生类似下面的日志:

2022-04-19T19:13:15.235+0800    DEBUG   policy  policy/const.go:18      NETWORK SETUP   {"name": "mainnet"}
2022-04-19T19:13:15.249+0800    INFO    cmd     internal/util_storage.go:279    sector s-t010000-17 located, sealed file in "a", cache dir in "a"
2022-04-19T19:13:15.249+0800    INFO    cmd     internal/util_storage.go:285    store instance exists   {"instance": "a"}
2022-04-19T19:13:15.249+0800    INFO    cmd     internal/util_storage.go:285    store instance exists   {"instance": "a"}

这就表示我们的导入和配置工作都已经完成了。

# 校验异常:扇区信息未记录成功

如果校验过程中出现类似

2022-03-11T16:45:59.120+0800    WARN    cmd     internal/util_storage.go:214    s-t010000-17 not found

这样的日志,说明指定的扇区未导入成功,我们需要重新检查导入过程。

# 校验异常:存储配置未更新

如果校验过程中出现类似

2022-03-11T16:22:34.044+0800    DEBUG   policy  policy/const.go:18      NETWORK SETUP   {"name": "mainnet"}
2022-03-11T16:22:34.059+0800    INFO    cmd     internal/util_storage.go:218    found s-t010000-17 in "a"
2022-03-11T16:22:34.059+0800    WARN    cmd     internal/util_storage.go:227    store instance not found, check your config file

这样的日志,说明 venus-sector-manager 的配置文件没有更新成功,我们需要按之前所说的方法去更新配置。