Volume removal errors

[serveriukai]

Current Behavior

Instead of disappearing from user interface list after removal volume becomes "unavailable"
with several hundred megabytes of data. Tried on two hosts - remaining data
557.84 MB / 420.00 GB on first,
285.21 MB / 470.00 GB on second.

To that moment data.dat files are already physically deleted from disk by hostd.

User interface alert example:

error: Failed to remove volume

timestamp
3/16/24, 4:23:25 PM
error
transaction failed (attempt 1): failed to remove volume sectors: volume is not empty
volume ID
15

migrated
106,021
failed
0
sectors
112057
used
106089

Corresponding system journal line:

Mar 16 16:41:30 tiny hostd[5271]: ERROR volumes.remove failed to remove volume {"volumeID": 15, "force": false, "error": "transaction failed (attempt 1): failed to remove volume sectors: volume is not empty"}

After restarting hostd service, journal entries:

Mar 16 17:12:49 tiny systemd[1]: Stopping hostd.service - hostd...
Mar 16 17:12:49 tiny systemd[1]: hostd.service: Deactivated successfully.
Mar 16 17:12:49 tiny systemd[1]: Stopped hostd.service - hostd.
Mar 16 17:12:49 tiny systemd[1]: hostd.service: Consumed 1h 32min 53.898s CPU time.
Mar 16 17:12:49 tiny systemd[1]: Started hostd.service - hostd.
Mar 16 17:12:49 tiny hostd[23511]: ERROR volumes unable to open volume {"error": "open /home/sia/fastdisk/data.dat: no such file or directory", "id": 15, "path": "/home/sia/fastdisk/data.dat"}

And volume still remains in volumes list with the same hundreds megabytes "unavailable".

Expected Behavior

Volume migrates data and disappears.

Steps to Reproduce

No response

Version

v1.0.3

What operating system did the problem occur on (e.g. Ubuntu 22.04, macOS 12.0, Windows 11)?

Debian 12

Anything else?

No response

[marius-wieschollek]

It also seems that this isn't just a reporting error, the data actually hasn't been migrated before the volume was deleted.

I ran an integrity check afterwards on the contracts and several of those now report missing blocks - which they didn't before.

[marius-wieschollek]

With the update to 1.0.4 the volumes are no longer deleted if they aren't empty, but it still takes at least two tries to delete a volume, even if there are no errors during the process.