[SOLVED] Error code 11 when moving storage from zfspool to local: "no space left on device" but there is plenty of space

I had the same problem moving proxmoxbackup LXC root disk from ZFS to Ceph. Other LXCs, so far, moved fine, but proxmoxbackup root did not. I then tried moving it to LVM, and it again died due to lack of space.

Maybe a warning in the log when a compressed volume is being moved to one without compression. "Moving from a compressed volume to a non-compressed volume can result in an out of space condition in the target volume if the new size exceeds the original size."

Or maybe in the documentation under the appropriate subjects (restores, move storage, etc.).
 
Last edited:
  • Like
Reactions: jsabater
I think that is an excellent idea, @BruceX. Any chance this warning message could be brought into the next version of Proxmox, @fabian? Once you've experienced the situation, it makes sense and you will probably not fall for it again, but for the first-timers it could be very helpful. :)
 
Last edited:
For future reference, Fabian means this:

Code: 
the problem is that the upper layer doesn't know whether the lower storage layer uses compression and how much it affects the data.

Still, my request would be to enable such information to be exposed. Not urgent, not critical, but when possible :)
 
FYI,
I had the same issue.
1. Couldn't migrate LXC since zfs storage was "not available on node".
2. Couldn't move volume to non-zfs storage. "No space left on device" errors.

Solution was to resized zfs volume to double it's size, and then I was able to move volume to a non-zfs storage, and then migrate to another Proxmox server in the cluster.

Note: I'm in the middle of adding a 3rd server to my cluster, and having them all setup with zfs.
 
You must log in or register to reply here.
Top Bottom