Recent content by Madhatter

  1. M

    PVE 9.2.2 unable to remove CT on zfs with "dataset is busy" error

    # fuser -vam /NVME-Pool/subvol-102-disk-0 USER PID ACCESS COMMAND /NVME-Pool/subvol-102-disk-0: root kernel mount /NVME-Pool LXC was not running. I was able to whack the CT from proxmox .. so only the storage is left but even manually I...
  2. M

    PVE 9.2.2 unable to remove CT on zfs with "dataset is busy" error

    Another interesting observation. I went to a CT, moved the disk to another storage, it moved fine but wasnt able to delete the old source. then I reassigned the old disk to any other CT (in my case I build a dummy CT) and then from theree I was able to delete the Disk on the NVME Pool. very...
  3. M

    PVE 9.2.2 unable to remove CT on zfs with "dataset is busy" error

    I did a bit more testing and I can move VMs off the storage. So this is specifically related to CTs.
  4. M

    PVE 9.2.2 unable to remove CT on zfs with "dataset is busy" error

    grep NVME-Pool/subvol-121-disk-0 /proc/*/mounts /proc/987/mounts:NVME-Pool/subvol-121-disk-0 /NVME-Pool/subvol-121-disk-0 zfs rw,noatime,xattr,posixacl,casesensitive 0 0 /proc/988/mounts:NVME-Pool/subvol-121-disk-0 /NVME-Pool/subvol-121-disk-0 zfs rw,noatime,xattr,posixacl,casesensitive 0 0...
  5. M

    PVE 9.2.2 unable to remove CT on zfs with "dataset is busy" error

    I'm not sure if this is a new problem as I havent tried to remove a CT for some while. But today I wanted to remove a few CTs which are running on a NVME ZFS and all result in "TASK ERROR: zfs error: cannot destroy 'NVME-Pool/subvol-121-disk-0': dataset is busy" Similar behavior on that...
  6. M

    VMs(CTs) cannot reach network over vmbr but host is fine

    Ich bin verzweifelt.... I have built a 3 node cluster PVE 8.4.1 (purely for low power, medium power and high power compute and to load VMS/CTs where needed) node 1 (low power, bond0 - 2 interfaces) is from the beginning working without issues. node 2 (medium power, bond 0 - 2 interfaces) once...
  7. M

    How to clean old ZFS rpool/ROOT/pve-1 rollback points?

    Dang, Sorry and Thanks a lot ... so I need to reconsider my layout.
  8. M

    How to clean old ZFS rpool/ROOT/pve-1 rollback points?

    Hi, I can't find anything here and in the docs and I noted that my rootdisk is slowly filling up with ZFS rpool snapshots / rollback points. I admit I never had to use them, and I'm sure they are useful .. But I don't need rollback to before Christy and I haven't found a way to configure a...
  9. M

    Adding non Proxmox hosts to Proxmox Ceph Pool

    Hi, I know this is not directly related to Proxmox rather than to Ceph, but I'll give it a try. In my home lab I have 1 Proxmox node (7.latest), and configured Proxmox ceph (Pacific) on it with 2 OSD I have 2 more non Proxmox hosts I would like to install ceph (?cephadm?) on and add those to...
  10. M

    pve-cluster startet nicht mehr

    ok ich glaube ich habs. Warning das ist echt hacky und ich sehe schon am Montag die Proxmox Jungs im Kreisel kotzen, wenn die das sehen. der Ordner /etc/pve/nodes/hostname wird vom pve-cluster service erstellt / gemanaged Pure Vermutung erstellt durch daten der /var/lib/pve-cluster/config.db...
  11. M

    pve-cluster startet nicht mehr

    Ich teste gerade ein wenig rum .. der host ist zwar renamed aber ich schaffe es nicht die Konfigurations Dateien in den neuen Ordner zu kopieren. das erstellen des ordners mit gestopptem PVE geht nicht.
  12. M

    pve-cluster startet nicht mehr

    BTW ich nutze das als Backup . da ist alles drinn, was ich brauche https://github.com/DerDanilo/proxmox-stuff
  13. M

    pve-cluster startet nicht mehr

    mkdir -p /etc/pve/nodes/alterhostname mkdir -p /etc/pve/nodes/neuerhostname pack in beide ordner deine backup daten rein edit: vergiss das hier das ist muell
  14. M

    pve-cluster startet nicht mehr

    Ich hab gerade mal schnell getestet. vi /etc/hosts vi /etc/hostname mit dem neuen hostname .. service pve-cluster restart hat nen fehler gebracht also einfach rebooted und proxmox kam mit dem neuen hostname einfach hoch .. Damals gabs die /var/lib/pve-cluster/config.db glaube noch nicht ..