Recent content by vongehlens

Morning all! Update: the NIC "Broadcom Inc. and subsidiaries NetXtreme II BCM5709 Gigabit Ethernet (rev 20)" was the root cause in my system. while getting desparate yesterday i took out that Broadcom BCM5709 4port card and replaced it with 2x 2port Intel 82571EB/82571GB. the shuffeling of...

little update... one further reboot of the proxmox server has shuffled one more interface... ens4f1 now became eth1 ... result: that vmbridge where ens4f1 was member did stop working... :confused:

Hello all, Upgrade done using the official steps to the letter. Upgrade ran without errors. PVE Server did boot and since my PVE server was not reachable anymore... OK, let go to the attick, get Monitor & keyboard, goto basement ...connect... Oha! … Maschine did reboot. good. Can login...

on my first PVE8 upgrade the Bookworm decided to rename all Interfaces and therefore the VMbridges did not work ... had ro go to the machine physically and fix the main vmbridge to get access again... i´ll post that story inside a separate threat.

Hallo zusammen, ich sehe das hier ausschließlich im Kontext PBS und ZFS. ein Dataset mit einer reservation wie oben vorgeschlagen anzulegen, scheint mir sinnvoller zu sein als ein Quota. Dies aber nur da ich noch nicht gefunden habe, sofern es möglich ist, ein Quota in % anzugeben. % ist aber...

Hallo Fabian, gleiches Problem hier... ein PBS ist voll gelaufen. Recovery läuft noch da ein bissler viele .Chunks. Idee/Frage: würde es nicht Sinn machen wenn Proxmox in den PBS einbaut das immer pro pool ein dataset "PBS-Recovery-Space" angelegt wird welches eine Reservation von 10gb hat aber...

@fiona and proxmox team: Thank you very much for adding this to the solution! I can confirm too that this new parameter "performance max-workers=N" has a significant effect to performance when doing backups (i also run ZFS pools). once i add "max-workers=1" or "max-workers=2" the backups will...

this is perfect Sir! thanks a lot again. i´ll test in a lab first for shure. cheers Stephan

ok, thanks. so 5 nodes with OSDs would then make sense to run replica of 5/3 as then each host carries one replic. - well, or i would need to deal with different CRUSH maps host/domains and stuff... not wanted at the moment. thanks for your guidance on the original request. Stephan

...hmmm. i understood the concept like this: the replication rule will store 3 replicas across all the 12 OSD across the cluster. if my interpretion is wrong then i´m fine. Like to have some confirmation / explanation of some more experienced Ceph admin than me. however, Ceph is quite...

Hi Jsterr, i like to have 5 copies to have a chance surviving the failure of up to 3 OSDs.... that was my intention. cheers Stephan

Hello Proxmox/Ceph admins, well, i´m not a newbie anymore with Proxmox, still like to learn and now need little help with Ceph pools. i´ve got three 3-node Ceph clusters here, all separate and in different sites. - all nodes are on Ceph 12.2.13 and PVE 6.4-13 all have one pool and 3/2 replica...

@brian: to my experience the dirty-bitmap is only used if a) the instance you like to backup was not rebooted from PVE since last backup and(!) b) not migrated from one to another cluster node since last backup. ...but i also like to learn if your issue might have another reason... rgds Stephan

Hi Ca_Maer, for Writing backups and being "nice" to your I/O you could use the IONICE variable inside the VZDUMP.conf. this should help to not limit the bandwidth while writing the backup but helping the source PVE host to priotize the VZdump differently differently (lower/higher) and "be nice"...

Hello all, i you read this you might be as desperate as i was because i´d found a chicken-and-egg problem at a friend who called me to fix his crashed PVE storage... here we go... Situation: - backups are done from PVE to Proxmox-backup-server (PBS) - needed to restore a VM backup without...