+29
−0
Loading
When we call the rpc command save_config, the current spdk environment will be saved, but the environment created by bdev_nvme_cuse_register is currently missing. In the production environment, SPDK usually auto-restarts with saved config file(by rpc.py save_config command) by systemd or docker. The missing NVMe cuse config leads to the lack of the additional spdk/cuse device once SPDK restarts. Change-Id: I0d4c9f279f99539426343af80e76bf42b400ef94 Signed-off-by:luchangqi.123 <luchangqi.123@bytedance.com> Signed-off-by:
zhenwei pi <pizhenwei@bytedance.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20039 Reviewed-by:
Jim Harris <jim.harris@samsung.com> Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Tomasz Zawadzki <tomasz.zawadzki@intel.com> Community-CI: Mellanox Build Bot