Recent content by micush

Yes, that was indeed it. It had gotten in through the use of a 3rd party LXC container. All gone now. Thanks for the pointer. Much appreciated.

Hi, cat /proc/$pid/cmdline shows kauditd0@pve and cat /proc/$pid/exe shows a bunch of compiled executable with no discernible information.

Hi, It appears I have one instance of kauditd0 for every LXC instance I have running after my PVE9 upgrade and they are consuming quite a bit of CPU: A search through the forums yields no results. Has anybody seen this one yet? How to fix it?

No Direct IO enabled here...

Like I said, I **want** to use virtiofs and get rid of NFS for this particular purpose, but the performance hit is just too great for me.

Yep. Cache=always is enabled. ZFS draid2 is being used as backing storage.

It's so slow compared to NFS. Like less than 1/4 the performance in my testing with FIO. I want to use it because it seems like a cleaner implementation on how to share files with the host. But, I cannot take that big of a performance hit. Shame really. DIRECT: server:/mnt/server1:# show disk...

Thanks for all the discussion. Good stuff. However, none of this is my point. I don't wish to discuss the merits of one storage type or another. I simply would like a usable snapshot feature when using a ZFS volume. It's totally doable. Just change the resulting dialog box and a little code...

Honestly, if they wanted to make it usable, get rid of the "failed" dialog box and replace it with a "This will remove these other snapshots if you want to rollback to here. Do you wish to continue? yes/no" As it stands it's not useful -- at least not from the GUI. Okay, the limitation exists...

This is not a true statement. Selecting a snapshot a few down the list does not destroy in-between snapshots. It simply fails the rollback operation with a popup that says "can't rollback, 'snapshot' is not the most recent snapshot on 'disk'." I *wish* it destroyed the in-between snapshots and...

What's the point of ZFS snapshots if only the very last one can be rolled back to? Seems kind of pointless.

I have a 5 node cluster that has been in production for more than 5 years now. Since PVE6, I'm starting to see things like this in my VM config files: [^A^@^@^@^@^@^@&^@^@^@^@^@^@^@^@^@^@^@nodes/lphxpve16/qemu-server/1150.conf^@agent: 1 balloon: 0 boot: dcn bootdisk: virtio0 cores: 15 ide2...

I'm on PVE 6.0.4. Great job on this release. The upgrade was relatively painless for me. I have a bunch of VMs under HA management. I bulk migrate these HA VMs from one host to another and set the Parallel Jobs value to 1 or more. All VMs are moved at once and the Parallel Jobs restriction is...

That is fantastic news. Thanks you so much.