Search results

this is not meant to to make users/customers uncertain about product quality , but whoever is deeper into using qcow2 may have a look at https://bugzilla.proxmox.com/show_bug.cgi?id=7012 , it's about a case where qcow2 performs pathologically slow and while searching for the cause, i found...

>i stil don't know why that 2nd network line causes is , and i don't think it is too interesting to know ? maybe asymetric routing ?

sorry, aber können wir hier evtl bitte doch lieber beim thema bleiben?

i would first disable net1 temporarly in the old and then provide 4 cores and 2048mb to the new lxc comparing two different operating systems is hard enough - but they should have the same lxc/hardware ressources i guess the most prominent different between the two lxc here should be samba...

you mean you have a second lxc container which works without problems? those are both turnkey linux lxc containers, or what? the one with the issue has docker inside?

we had a ticket for this at https://bugzilla.proxmox.com/show_bug.cgi?id=3118, which i just closed. if anybody still sees this with any recent linux distro, please report. (i guess this exists, as bugs constantly (re)appear in linux) ;)

also mind https://bugzilla.proxmox.com/show_bug.cgi?id=4482 and https://bugzilla.proxmox.com/show_bug.cgi?id=3859

für zukünftige "lessons learned" sowie das damit verbundene "copy&paste" um es für andere leichter rüberzubringen: Es ist ein bekanntes Problem, dass bei größeren Updates docker-Container in LXC-Containern immer mal wieder kaputt gehen. Beide nutzen die gleichen Teile des Kernels, daher ist...

@floh8 , i agree that btrfs my be faster then zfs with small file / metadata access, but i would not consider that worth trying until proxmox verfiy didn't get optimization for better parallelism. you won't change your large xx terabytes datastore when in production....

@triggad , do you use the latest version of PBS ? there has been at least this enhancement which can increase gc speed a lot https://git.proxmox.com/?p=proxmox-backup.git;a=commit;h=03143eee0a59cf319be0052e139f7e20e124d572 Total GC runtime shows significatn reduction (average of 3 runs)...

could you post your lxc container configuration, your samba configuration from inside container and your storage.cfg from /etc/pve and the output of the "mount" command ?

@nalysarbur , can you please post the contents of your both virtual machine configuration files from /etc/pve/qemu-server , your storage.cfg and the output of pvs/vgs/lvs commands ?

how can efi storage on lvm have disk format qemu2 ? when i select efi storage on lvm, it automatically switches to raw and is greyed in your video it looks like this

does somebody know if this is still an issue with DRBD ? https://github.com/LINBIT/drbd/issues/125

hi, for a long time, i'm a little bit annoyed that there is quite a reasonable number (2724) of open , unresolved tickets in proxmox bugzilla at https://bugzilla.proxmox.com i don't want to blame proxmox team here, but my question is , how we can put some systematic work into this to better...

yes it did

damn, i must have overseen that. thanks for the pointer

we upgraded from 8 to 9 a while ago, this time i did just apt update/upgrade and got this message. don't know if this is new or did exist since the upgrade from 8 to 9 reboot does not fix it - still get this message on entering psql tool root@pmg:~# su - postgres postgres@pmg:~$ psql WARNING...

Hello, on latest updates i get WARNING: database "postgres" has a collation version mismatch DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41. HINT: Rebuild all objects in this database that use the default collation and run...

> proxmox rescue boot no such device pool @corianito , do you mean rescue boot menu entry from pve9 installation iso?