public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Frank Thommen <f.thommen@dkfz-heidelberg.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Cannot delete snapshot from aborted snapshot creation process
Date: Mon, 3 Apr 2023 11:58:12 +0200	[thread overview]
Message-ID: <87f8c27c-0446-ee42-42fd-effd9fc75f59@dkfz-heidelberg.de> (raw)
In-Reply-To: <2B638193-F28F-4F96-BE6E-9E6DE9F8F7CA@elchaka.de>

Thanks for the hint, but I am still at a loss here. I haven't 
(knowingly) configured any pools (*). The VM has two virtual disks, 
listed as

   Hard Disk (scsi0): ceph-rbd:vm-118-disk-0
   Hard Disk (scsi1): ceph-rbd:vm-118-disk-1

in the dashboard (Hardware tab). But with a similar `rbd` command I get 
an error:

$ rbd snap ls ceph-rbd/vm-118-disk-0
rbd: error opening pool 'ceph-rbd': (2) No such file or directory
$ rbd snap ls ceph-rbd/vm-118-disk-1
rbd: error opening pool 'ceph-rbd': (2) No such file or directory
$

I could not find an `rbd` subcommand to list all available pools.


(*) well, there is one resource pool "mypool" which I have created when 
playing around a long time ago, but there are no members in that pool 
(see attached screenshot)


Any hint on how to proceed from here?

Frank



On 01.04.23 01:35, Mehmet wrote:
> The you should look if the snap really exist.
> I.e.
> 
> Rbd snap ls yourpoo/vm-123-disk-0
> 
> Of it realy not exist you can manualy edit the .conf file of your vm 
> under /etc/pve/qemu-server/123.conf
> 
> Hth
> Mehmet
> 
> Am 31. März 2023 08:34:04 MESZ schrieb Frank Thommen 
> <f.thommen@dkfz-heidelberg.de>:
> 
>     it's ceph
> 
>     On 31.03.23 01:27, Lindsay Mathieson wrote:
> 
>         Whats the underlying storage? zfs? ceph?
> 
>         On 31/03/2023 2:52 am, Frank Thommen wrote:
> 
>             I aborted the creation of a snapshot (started and stopped
>             through web UI, PROXMOX version is 7.3-3). No I cannot
>             delete this snapshot any more:
> 
> 
>     ------------------------------------------------------------------------
>     pve-user mailing list
>     pve-user@lists.proxmox.com
>     https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user  <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>
> 
From f.thommen@dkfz-heidelberg.de  Mon Apr  3 12:26:07 2023
Return-Path: <f.thommen@dkfz-heidelberg.de>
X-Original-To: pve-user@lists.proxmox.com
Delivered-To: pve-user@lists.proxmox.com
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits))
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id 93F22917C4
 for <pve-user@lists.proxmox.com>; Mon,  3 Apr 2023 12:26:07 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id 6F80F3E873
 for <pve-user@lists.proxmox.com>; Mon,  3 Apr 2023 12:25:37 +0200 (CEST)
Received: from mailhost2.inet.dkfz-heidelberg.de
 (mailhost2.inet.dkfz-heidelberg.de [193.174.53.133])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS
 for <pve-user@lists.proxmox.com>; Mon,  3 Apr 2023 12:25:36 +0200 (CEST)
Received: from mx-ext.inet.dkfz-heidelberg.de (mx-ext.inet.dkfz-heidelberg.de
 [192.54.49.101])
 by mailhost2.inet.dkfz-heidelberg.de (8.14.7/8.14.7) with ESMTP id
 333APawo010466
 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL)
 for <pve-user@lists.proxmox.com>; Mon, 3 Apr 2023 12:25:36 +0200
X-Virus-Scanned-DKFZ: amavisd-new at dkfz-heidelberg.de
X-External-Client-Name: addr16.inet.dkfz-heidelberg.de
DKIM-Filter: OpenDKIM Filter v2.11.0 mx-ext.inet.dkfz-heidelberg.de
 333APX8g022952
Received: from [172.22.47.211] (addr16.inet.dkfz-heidelberg.de
 [193.174.55.143]) (authenticated bits=0)
 by mx-ext.inet.dkfz-heidelberg.de (8.14.7/8.14.7/smtpin) with ESMTP id
 333APX8g022952
 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
 for <pve-user@lists.proxmox.com>; Mon, 3 Apr 2023 12:25:34 +0200
Message-ID: <ad5a17bd-deb3-0d0c-085b-4498de08012b@dkfz-heidelberg.de>
Date: Mon, 3 Apr 2023 12:25:33 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.9.1
To: pve-user@lists.proxmox.com
References: <78e2e3ac-e77e-78e6-48d2-395c66384857@dkfz-heidelberg.de>
 <c7617126-2a6b-5723-02e2-594b8224478e@gmail.com>
 <1b67a412-cf53-0b44-6e74-c1ee4c6223a6@dkfz-heidelberg.de>
 <2B638193-F28F-4F96-BE6E-9E6DE9F8F7CA@elchaka.de>
 <87f8c27c-0446-ee42-42fd-effd9fc75f59@dkfz-heidelberg.de>
From: Frank Thommen <f.thommen@dkfz-heidelberg.de>
Organization: DKFZ Heidelberg, Omics IT and Data Management Core Facility
 (ODCF)
In-Reply-To: <87f8c27c-0446-ee42-42fd-effd9fc75f59@dkfz-heidelberg.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2
 (mx-ext.inet.dkfz-heidelberg.de [192.54.49.101]);
 Mon, 03 Apr 2023 12:25:34 +0200 (CEST)
X-Spam-Status: No, score=-102.4 required=5.0 tests=ALL_TRUSTED,NICE_REPLY_A,
 URIBL_BLOCKED autolearn=disabled version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
 mx-ext.inet.dkfz-heidelberg.de
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.595 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_ASCII_DIVIDERS 0.8 Email that uses ascii formatting dividers and possible
 spam tricks
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 NICE_REPLY_A            -2.37 Looks like a legit reply (A)
 RCVD_IN_DNSWL_MED        -2.3 Sender listed at https://www.dnswl.org/,
 medium trust
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [PVE-User] Cannot delete snapshot from aborted snapshot
 creation process
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, 
 <mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Mon, 03 Apr 2023 10:26:07 -0000

In the meantime I found `ceph osd lspools`, which lists

1 pve-pool1
2 cephfs_data
3 cephfs_metadata
4 device_health_metrics

(shouldn't one be able to see that somewhere in the PVE UI?)

and there doesn't seem to be any snapshots there:

$ rbd snap ls pve-pool1/vm-118-disk-1
$ rbd snap ls pve-pool1/vm-118-disk-0
$

I have deleted the snapshot from /etc/pve/qemu-server/118.conf and now 
it's also gone from the UI.

Thanks a lot, Frank


On 03.04.23 11:58, Frank Thommen wrote:
> Thanks for the hint, but I am still at a loss here. I haven't 
> (knowingly) configured any pools (*). The VM has two virtual disks, 
> listed as
> 
>    Hard Disk (scsi0): ceph-rbd:vm-118-disk-0
>    Hard Disk (scsi1): ceph-rbd:vm-118-disk-1
> 
> in the dashboard (Hardware tab). But with a similar `rbd` command I get 
> an error:
> 
> $ rbd snap ls ceph-rbd/vm-118-disk-0
> rbd: error opening pool 'ceph-rbd': (2) No such file or directory
> $ rbd snap ls ceph-rbd/vm-118-disk-1
> rbd: error opening pool 'ceph-rbd': (2) No such file or directory
> $
> 
> I could not find an `rbd` subcommand to list all available pools.
> 
> 
> (*) well, there is one resource pool "mypool" which I have created when 
> playing around a long time ago, but there are no members in that pool 
> (see attached screenshot)
> 
> 
> Any hint on how to proceed from here?
> 
> Frank
> 
> 
> 
> On 01.04.23 01:35, Mehmet wrote:
>> The you should look if the snap really exist.
>> I.e.
>>
>> Rbd snap ls yourpoo/vm-123-disk-0
>>
>> Of it realy not exist you can manualy edit the .conf file of your vm 
>> under /etc/pve/qemu-server/123.conf
>>
>> Hth
>> Mehmet
>>
>> Am 31. März 2023 08:34:04 MESZ schrieb Frank Thommen 
>> <f.thommen@dkfz-heidelberg.de>:
>>
>>     it's ceph
>>
>>     On 31.03.23 01:27, Lindsay Mathieson wrote:
>>
>>         Whats the underlying storage? zfs? ceph?
>>
>>         On 31/03/2023 2:52 am, Frank Thommen wrote:
>>
>>             I aborted the creation of a snapshot (started and stopped
>>             through web UI, PROXMOX version is 7.3-3). No I cannot
>>             delete this snapshot any more:
>>
>>
>>     
>> ------------------------------------------------------------------------
>>     pve-user mailing list
>>     pve-user@lists.proxmox.com
>>     https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user  
>> <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>
>>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user



      parent reply	other threads:[~2023-04-03  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 16:52 Frank Thommen
     [not found] ` <c7617126-2a6b-5723-02e2-594b8224478e@gmail.com>
2023-03-31  6:34   ` Frank Thommen
     [not found]     ` <2B638193-F28F-4F96-BE6E-9E6DE9F8F7CA@elchaka.de>
2023-04-03  9:58       ` Frank Thommen [this message]

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=87f8c27c-0446-ee42-42fd-effd9fc75f59@dkfz-heidelberg.de \
    --to=f.thommen@dkfz-heidelberg.de \
    --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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal