Search results

What ST8000? Something like a ST8000DM004 uses SMR and shouldn't be used with ZFS or any raid or server workload. Write performance of SMR HDDs will drop to a horrible level once the caches got filled up. Especially terrible in case of a resilver where you need to rewrite the wholedisk continously.

You might want to have a look at: https://github.com/openzfs/zfs/pull/15022 https://www.tspi.at/2022/11/26/whynosmrforzfs.html

No, that feature is still not rolled out yet. You will have to wait for it or destroy and recreate your pool. By the way...those HDDs use shingled magnetc recording (SMR) and shouldn't be used with ZFS...or any other server workload... I would recommend you google for the difference between CMR...

For better DB performance you might also want to set the recordsize and volblocksize to the blocksize your DB is reading/writing records. If you want this to persist restores I would recommend to create another dataset and add that as a new storage of type ZFS. Then set the recordsize of that...

Falls du Grub mit dem proxmox-boot-tool nutzt kannst du mit proxmox-boot-tool kernel pin 6.5.13-5-pve den Kernel permanent anpinnen : https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_kernel_pin

Yes, running a PBS VM with local block storage is working. Some years ago when, I was using that, you had to install PBS on top of a Debian VM because the PBS ISO installer wasn't working on TrueNAS Core.

There is a typo: "iface vmdr0 inet static" instead of "iface vmbr0 inet static"

Also bisher durfte man keine Sync Jobs bei den kostenlosen Test Datastores haben. Bei den bezahlten ging es und man musste sich glaube ich dafür an den Tuxis Support wenden. Und soweit ich weiß nur ein einziges kostenloses PBS.

I wrote a hook script as a workaround that will shutdown all VMs sharing a VM, then do the backup job and later start that VM again that got shutdown. That way the backup job won't fail and all VMs will be backed up. But you of cause got downtime as the running VM still needs to be shut down so...

Nicht empfehlenswert, aber ja...geht. Entweder beides Bare Metal parallel (siehe hier: https://pbs.proxmox.com/docs/installation.html#install-proxmox-backup-server-on-proxmox-ve) oder als VM. PBS als LXC sollte man eher meiden. Ist auch nur ein Klick, aber zu beachten ist, dass du mit PBS keine...

Any PCI passthrough in use for that VM? Because this requires allocating all RAM at start because of DMA.

ESXi is designed for this. PVE isn't.

Ja, dann halt entsprechend weniger VMs starten.

Außerdem mal memtest86+ booten und über Nacht laufen lassen. Systeminstabilitäten sind oft defekter RAM (gerade wenn du kein ECC hast, dass da Fehler gefixt werden könnten) oder defektes Netzteil mit Spannungsschwankungen was dann zum Brownout führt.

Those are SMR HDDs. Don't use SMR HDDs for anything if possible, especially not for server workloads or ZFS. CMR HDDs only exists up to 2.4TB in 2.5" form factor. Once the CMR-cache is full those SMR HDDs will totally suck and can't keep up writing.

Don't install it on pen drives, SD cards and similar. PVE writes a lot and will kill those quickly. With ZFS for raid1 it it might even kill small/cheap consumer SSDs pretty fast. Get proper HDDs or SSDs. I usually recommend to use 32GB for the root fileystem. If you want to upload big ISOs or...

Then its a single disk vdev and not a raidz (which would be the equivalent of a raid5). You can't. Backup everything, destroy that pool, recreate it as a 3-disk raidz and do a restore. But be aware that you won't be able to add a 4th/5th disk later (yet).

Yes. Or "pvesm set <YourStorageID> --is_mountpoint <AbsolutePathToMountpoint>" in case the folder your are using as a directory storage isn't the mountpoint itself but a folder below it.

No, read the link. Its a database and it contents are presented via fuse as files. Without the PVE service running (and it won't when booting something else than PVE) there won't be any files. Find out what's consuming the space, delete that stuff, reboot and see if it is working again. And if...

That's not unusual as that's not a normal folder and the pve-cluster.service needs to be running for it to be mounted and this often isn't the case with a full root flesystem. See: https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs)