From: "JR Richardson" <jmr.richardson@gmail.com>
To: <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Unused Disk Remove vs Detach SOLVED
Date: Sat, 23 Jan 2021 10:07:26 -0600 [thread overview]
Message-ID: <000201d6f1a1$d80b0d80$88212880$@gmail.com> (raw)
* JR Richardson <jmr.richardson@gmail.com> [210115 17:57]:
> I'm running PVE 6.2.11, I have VMs with Disks on NFS shared storage. I
> moved disks to other storage nodes but did not choose to delete the
> old disk, so the old disk is still assigned to the VM in hardware as
> 'Unused Disk 0'. When I select the disk, the 'Detach' button changes
> to 'Remove'. I remember in older versions of PVE, you could just
> 'Detach' disks instead of removing them. Is this due to the old
> storage node is still on-line? If I shutdown the old storage node,
> would I get the option to Detach Unused Disks?
I can only speculate, but essentially, completely detached disks are
invisible to PVE. I believe, on subsequent actions - like disk
moves, VM migrations, ... - the disk "numbers" can be reused. If
there's such an old disk around, the operation might either fail or
the disk might be silently overwritten.
From this PoV, I would strongly recommend against fully detaching
disks from VMs.
> Can I get around this via command line utility to detach the old disk?
You can edit the VM definition file and remove the unusedN: line.
Best,
Chris
Hi Chris, I removed the unused disk from the VM.conf file and that
immediately removed it from the GUI. I shut down the storage node and kept
all my disks intact without errors.
Thanks.
JR
JR Richardson
Engineering for the Masses
Chasing the Azeotrope
JRx DistillCo
1'st Place Brisket
1'st Place Chili
reply other threads:[~2021-01-23 16:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000201d6f1a1$d80b0d80$88212880$@gmail.com' \
--to=jmr.richardson@gmail.com \
--cc=pve-user@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox