8000
Skip to content

zfs.clone_copy=rebase option does not work for copying volumes #16449

@dmitry-lyfar

Description

@dmitry-lyfar

Please confirm

  • I have searched existing issues to check if an issue already exists for the bug I encountered.

Distribution

Ubuntu

Distribution version

24.04

Output of "snap list --all lxd core20 core22 core24 snapd"

core20  20250526     2599   latest/stable  canonical✓  base
core22  20250612     2045   latest/stable  canonical✓  base,disabled
core22  20250730     2111   latest/stable  canonical✓  base
core24  20250618     1055   latest/stable  canonical✓  base,disabled
core24  20250729     1151   latest/stable  canonical✓  base
lxd     6.5-72c8a10  35210  6/stable       canonical✓  -
snapd   2.70         24792  latest/stable  canonical✓  snapd,disabled
snapd   2.71         25202  latest/stable  canonical✓  snapd

Output of "lxc info" or system info if it fails

N/A

Issue description

It does not look like that the rebase option described here works for the zfs LXD driver as it's practically a dead branch of code. See

if d.config["zfs.clone_copy"] == "rebase" {
The execution will never get here if the option is set (see lines 677 and 661 that make that branch impossible to reach).

do_storage_driver_zfs() does not test this mode for copy scenarios.

Steps to reproduce

N/A

Information to attach

  • Any relevant kernel output (dmesg)
  • Instance log (lxc info NAME --show-log)
  • Instance configuration (lxc config show NAME --expanded)
  • Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log)
  • Output of the client with --debug
  • Output of the daemon with --debug (or use lxc monitor while reproducing the issue)

Metadata

Metadata

Assignees

Labels

JiraTriggers the synchronization of a GitHub issue in Jira

Type

No fields configured for Bug.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0