Recent content by flamozzle

  1. F

    [SOLVED] Destroy OSD wiped journal/db drive partition table

    I can confirm that pve-manager 5.3-11 no longer exhibits this problem. Thanks, Alwin.
  2. F

    [SOLVED] Destroy OSD wiped journal/db drive partition table

    I have now reproduced this on a different server in the same (proxmox and ceph) cluster. Here is the second example, following the same procedure as before, but on a different server and with a different OSD (tho it was again a bluestore OSD). In this case /dev/sde is the OSD and /dev/sdd is...
  3. F

    [SOLVED] Destroy OSD wiped journal/db drive partition table

    I have since realized that the damage was more extensive than I originally thought. Because the disk wipe writes 200MiB at the beginning of the disk, it would also corrupt the first partition on the journal/db disk. In my case, I was incredibly fortunate to have an old unused partition as...
  4. F

    [SOLVED] Destroy OSD wiped journal/db drive partition table

    This happened on proxmox 5.3-6, a cluster of 3 servers with ceph OSDs on two of the servers. I was destroying a bluestore OSD to re-create it as a filestore OSD. The system had a mixture of filestore and bluestore OSDs. I did everything using the web UI. I stopped the OSD, out-ed it. Then I...
  5. F

    After upgrade to proxmox 4.x, backup=no no longer works

    (Update), I had searched before, but missed that there was already a similar report of this problem, with info on a pending fix. It is in the thread entitled exclude disk from qemu backup on Proxmox 4 https://forum.proxmox.com/threads/exclude-disk-from-qemu-backup-on-proxmox-4.25807/
  6. F

    After upgrade to proxmox 4.x, backup=no no longer works

    Since upgrading a small home cluster to proxmox 4 (4.1-5), the storage that had "backup=no" are no longer being skipped during backups. Additionally, when I check "No backup" in the web UI after the upgrade, it puts backup=0 in the conf file. But then it doesn't recognize that when I later...