Search results

i learned today that csum errors with btrfs can occur if DIRECTIO (ie cache=none) is being used with btrfs. https://bugzilla.redhat.com/show_bug.cgi?id=1914433

i have observed a similar performance issue on zfs shared via samba, unfortunately i'm not yet able to reproduce. when live migrating a qcow2 virtual disk hosted on zfs/samba share to disk to local ssd, i observed pathological slowness and saw lot's of write IOPs on the source (!) whereas i...

there is another bugticket at https://bugzilla.proxmox.com/show_bug.cgi?id=4805, but it has wrong state as "more info needed" does not apply, i have no more info to provide besides the query for obsoleting virtual ide cdrom for freshly created VMs.

what is the recommended or most popular tool to orchestrate/automate vm setup/deployment in proxmox ? what do proxmox customers / hosters use ? terraform? ansible? puppet? vagrant?

if you like , you can register gitlab account and report your own experience with that issue, that would raise awareness on this issue

@brucekornfeld , did stormagic ever think on providing some free svsan license small virtual storage amount (i guess <<500gb and usage limitation for non prod is ok) for hobbyists and tech enthusiasts ? ( like leftand did for example...

>This can have some pretty unpleasant write performance implications. in which way? lzo is blazingly fast and zstd is also fast on modern cpu. >better to let the compression algorithm decide but the compression heuristics in btrfs sucks, especially when used in conjunction with large virtual...

>I think what @alexskysilk is referring to is a small physical disk, which is not the same as qdevce technology wise. that small phyiscal disk needs to be "shared" between the two nodes, and with that requirement, it's not "small" anymore, as i need either NAS or SAN attached disk. that's the...

>In truth, I have often wondered why no such option exists for pve but it does? besides qdevice (which does not integrate well into proxmox, as you won't notice failure easily fore example), you can have full blown pve on any old small x86 box/thin client out there for well under 20 bucks and...

> If I need a witness for high availability, I need a third "node." but a full blown 3rd node is something you don't want to have in SMB/ROBO environemnt. in the past, with SvSan you could even have the witness off-site, iirc. so, you could have a full pve installation on some tiny, old and...

> Why am I running yet another cluster in a cluster? in which way is ceph different from being a "cluster in a cluster" ?

>If I need a machine to run a witness on, why not just run Ceph on it? because you can't run ceph on a low cost, low power machine like raspberry pi. >So essentially, this is a blatant vendor advertisement of a commercial solution that is "easier than Ceph", yet has none of the features Ceph...

yes, it is using iscsi, but there is LVM shared volume group on top of that, so that should not be a problem !? https://support.stormagic.com/hc/en-gb/articles/16343256511261-Deploying-a-2x-node-witness-Proxmox-and-SvSAN-HA-cluster-Part-5-Storage-Provisioning

now , there is something interesting going on with ksm. new features will arrive in kernel 6.8 The KSM Guide at already mentions that at https://docs.kernel.org/admin-guide/mm/ksm.html see ...

i know of all the knobs, i want to help improve the product for everybody and stop wasting cpu and/or energy

>There are some knobs that can limit ksmd, like multiplying KSM_SLEEP_MSEC (put a 0 behind it) and lowering KSM_NPAGES_MAX in /etc/ksmtuned.conf @leesteken , yes i know, but this post is not about individually tuning KSM , it's about making it work correctly by default >Are you sure it is not...

thanks, but this post is not about getting rid of ksm but about making it more cpu friendly and sorting out issues in conjunction with ZFS, i.e. make it behave better by default. this is taken from my servers. on more then half of them, ksmd is the top cpu consumer - though ARC size is...

hello, see subject. there are these two bugreports / RFEs which did not get any attention for a long time now 1. RFE: ZFS ARC size not taken into account by pvestatd or ksmtuned https://bugzilla.proxmox.com/show_bug.cgi?id=3859 2. ksmtuned using vsz instead of rss...

you have a discrepancy between zfs tools and zfs kernel modules # zfs -V will show did you do apt dist-upgrade ?

it tried it some days ago and it's a pain in the ass and it's also broken with 8.1.x https://github.com/Telmate/terraform-provider-proxmox/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc