You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I updated to v2.0.3 created an empty volume of 1TB. I realized it's in the wrong directory, so I deleted it. For 10 minutes I monitored the disk activity (zfs iostat storage 1) and I saw almost no activity. I switched back to v.2.0.2 and delete worked. I know 2.0.2 sometimes fails to move the storage from one volume to another, but retry works. 2.0.3 doesn't seem to do anything when deleting empty volume (or downsizing)
Expected Behavior
Deleting should be able to complete in 10 minutes as the previous version worked for less than a minute. also there should be disk and/or cpu activity
Steps to Reproduce
update to 2.0.3
create new empty volume
delete the empty volume.
Version
v2.0.3
What operating system did the problem occur on (e.g. Ubuntu 22.04, macOS 12.0, Windows 11)?
docker on debian 12
Anything else?
I didn't wait long enough to see if delete is going to succeed.
The text was updated successfully, but these errors were encountered:
Current Behavior
After I updated to v2.0.3 created an empty volume of 1TB. I realized it's in the wrong directory, so I deleted it. For 10 minutes I monitored the disk activity (zfs iostat storage 1) and I saw almost no activity. I switched back to v.2.0.2 and delete worked. I know 2.0.2 sometimes fails to move the storage from one volume to another, but retry works. 2.0.3 doesn't seem to do anything when deleting empty volume (or downsizing)
Expected Behavior
Deleting should be able to complete in 10 minutes as the previous version worked for less than a minute. also there should be disk and/or cpu activity
Steps to Reproduce
Version
v2.0.3
What operating system did the problem occur on (e.g. Ubuntu 22.04, macOS 12.0, Windows 11)?
docker on debian 12
Anything else?
I didn't wait long enough to see if delete is going to succeed.
The text was updated successfully, but these errors were encountered: