all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Lorne Guse via pve-devel <pve-devel@lists.proxmox.com>
To: "Max R. Carrara" <m.carrara@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Lorne Guse <boomshankerx@hotmail.com>
Subject: Re: [pve-devel] busy dataset when trying the migrate iscsi disk
Date: Wed, 17 Sep 2025 17:47:25 +0000	[thread overview]
Message-ID: <mailman.129.1758131291.390.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <DCV27TADGMZB.2L2IWM3VIM6LH@proxmox.com>

[-- Attachment #1: Type: message/rfc822, Size: 12569 bytes --]

From: Lorne Guse <boomshankerx@hotmail.com>
To: "Max R. Carrara" <m.carrara@proxmox.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: busy dataset when trying the migrate iscsi disk
Date: Wed, 17 Sep 2025 17:47:25 +0000
Message-ID: <DM6PR17MB3466AF450A03DC5A752C4B3BD017A@DM6PR17MB3466.namprd17.prod.outlook.com>

Ironically the patch version of the plugin actually utilizes the native Proxmox code in ZFSPlugin.pm / ZFSPoolPlugin.pm for managed the zvol dataset. The patch version only manages the iSCSI configuration.

I think the best course is to consider the patch version legacy and focus on the new fully API driven Custom Storage Plugin.

TrueNAS indicated there are plans to implement some form of UI hooks for Custom Storage Plugins. This is very encouraging.
________________________________
From: Max R. Carrara <m.carrara@proxmox.com>
Sent: Wednesday, September 17, 2025 6:04 AM
To: Lorne Guse <boomshankerx@hotmail.com>; Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: busy dataset when trying the migrate iscsi disk

On Mon Sep 15, 2025 at 5:34 AM CEST, Lorne Guse wrote:
> I'm working on TrueNAS over iSCSI for Proxmox and have run into an issue migrating disks. When trying to delete the old storage, which has just successfully been transfered, the iscsidirect connection must remain open because we are getting:
>
> cannot destroy 'slow/vm-188-disk-0': dataset is busy
>
> Is there a way to ensure the iscsidirect connection is closed before trying to delete the underlying zfs dataset?

Hi Lorne! Glad to see you on the mailing list!

I've sifted around our code to see how we handle this, and it seems that
we're simply retrying a couple of times until the dataset is actually
deleted [0]. I think that might be your best bet, though if you find an
alternative, I'd be curious to know.

[0]: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.proxmox.com%2F%3Fp%3Dpve-storage.git%3Ba%3Dblob%3Bf%3Dsrc%2FPVE%2FStorage%2FZFSPoolPlugin.pm%3Bh%3Dd8d8d0f9fc1cc6f1a02d8f5800c388b355609bf5%3Bhb%3Drefs%2Fheads%2Fmaster%23l362&data=05%7C02%7C%7C08ddb2ac62744e0c4a2908ddf5e259ac%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638937074705932603%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=dV3Ch024RrnvSKKDsT4k1zP23S%2BCX9jFR6YISZ5Lpe0%3D&reserved=0<https://git.proxmox.com/?p=pve-storage.git;a=blob;f=src/PVE/Storage/ZFSPoolPlugin.pm;h=d8d8d0f9fc1cc6f1a02d8f5800c388b355609bf5;hb=refs/heads/master#l362>



[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-09-17 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DM6PR17MB34662B3F92B53FF3394433C4D015A@DM6PR17MB3466.namprd17.prod.outlook.com>
2025-09-17 12:04 ` Max R. Carrara
2025-09-17 17:47   ` Lorne Guse via pve-devel [this message]
     [not found]   ` <DM6PR17MB3466AF450A03DC5A752C4B3BD017A@DM6PR17MB3466.namprd17.prod.outlook.com>
2025-09-18 17:52     ` Max R. Carrara
2025-09-15  3:34 Lorne Guse via pve-devel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mailman.129.1758131291.390.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=boomshankerx@hotmail.com \
    --cc=m.carrara@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal