'Incus storage volume move' seems stalled

1

I’m moving a very large volume ~ 8TB, and started it yesterday. i can see about 4.3 TB has moved, but it seems stalled. The command still appears active in the terminal, but when I check network activity, I don’t see the 120Mb/s that I was seeing yesterday

Is there any thing I can do to get the data moving again without lossing my data from the Volume?

Source Info

info:
  description: Storage
  driver: zfs
  name: ncloud_storage
  space used: 8.81TiB
  total space: 10.44TiB
used by:
  volumes:
  - media_store

Target Info:

info:
  description: Main Storage Pool
  driver: zfs
  name: main_store
  space used: 4.45TiB
  total space: 31.58TiB
used by:
  volumes:
  - media_store

Any help is greatly appreciated.

2

Check ps fauxww on both the source and target.

As you’re going with ZFS to ZFS, you should see a pair of zfs send and zfs receive processes running under the main Incus process.

Also go look at incusd.log on both the source and target as well as incus operation list again on both source and target.

3

Here’s incus operation list

TARGET:

+--------------------------------------+------+------------------------+---------+------------+----------------------+
|                  ID                  | TYPE |      DESCRIPTION       |  STATE  | CANCELABLE |       CREATED        |
+--------------------------------------+------+------------------------+---------+------------+----------------------+
| 0ff47b29-d5d1-4fd9-b228-3751f94b0fcb | TASK | Copying storage volume | RUNNING | NO         | 2026/01/01 20:51 UTC |
+--------------------------------------+------+------------------------+---------+------------+----------------------+

Source

+----+------+-------------+-------+------------+---------+
| ID | TYPE | DESCRIPTION | STATE | CANCELABLE | CREATED |
+----+------+-------------+-------+------------+---------+

This makes me think something has gone awry

less /var/log/incus/incusd.log

Source:

  • blnak, no entries.
  • in incusd.log.1 the last entry was from 12/30/25, 2 days before I started this move.

Target:

  • Blank

ps fauxww

Target:

root        6938  5.5  0.0  15492  6400 ?        S    Jan01  72:37  \_ zfs receive -x mountpoint -F -u main_store/custom/default_media_store

Source:

  • No entry for anything with afs

So, seems like the sending side had an issue, but for whatever reason didn’t kill the command I ran which is

ncus storage volume move ncloud_storage/media_store 4-bay-tm:main_store/media_store

As it still appears to be active in the terminal ssh window I used.

Now what?

4

Can I just re-run the command and it will complete, or will it error saying the volume already exists since it appears to be partially done?

5

Kill the zfs receiveprocess on the receiving side, then you can try again.
It would likely eventually hit a timeout, but that may take a while :wink:

6

Okay, stopped the receive side, then killed the stuck send, and tried to start it again, but get

Error: Failed storage volume creation: Volume by that name already exists

7

it appears the whole volume is still on the original. So, in incus does it not move anything until the whole thing is complete?

8

A move is a copy+delete, so the source data would only go away at the end.
That avoids data loss if something goes wrong.

1 Like