Search results

I just noticed that ksmtuned was missing after upgrade to PROXMOX 6

As I told in 0.7 changing ARC size its almost immediately. After this I set ARC size back with echo to 12G but ARC stuck with 5/6. 4 hours passed. I think some new settings must be involved with that.

Current ARC # arc_summary ------------------------------------------------------------------------ ZFS Subsystem Report Thu Aug 08 10:27:10 2019 Linux 5.0.18-1-pve 0.8.1-pve1 Machine: nmz-lt (x86_64)...

After upgrade ZFS 0.8 works differently vs 0.7. I set ARC size with echo parameter and new changes in 0.8 is effected not immediate.

Yes, more disk = more speed/IO. But creating ZFS you must think about how much time you have until you change death/damaged disk. Like Raidz3 give more time compare to others options. I had strange situation then one disk go offline because of unknown reason and ZFS stops writing to it. Pool...

This is single pool and its very unbalanced in every way. You mush choose what you want. If your bugged allows 5 x big SSD then do Raidz2.

I`m old fashion user. I do it manually with aptitude and I see no problem with it. The new changes will help you :-)

The usage of the ZFS pool impact performance but not the errors.

Why you use LVM in VM and then XFS? Maybe that makes bugs.

/etc/rc.local is very old startup script. And I like it.

Does your HBA shows disks? Can you boot from cdrom/usb/(disk attached to motherboard)?

Are you sure you need dedup? It require RAM .... a lot.

If you will set dedup for pool it will be inherited for lowers levels of fs/volumes. Except if you set for everyone manually.

Another solution is to use single ZFS file system with dedup and use it as directory mount point in Proxmox. Use VM disk as images (raw,qcow2,vmdk)

You can change ARC size live with: #echo 2147483648 > /sys/module/zfs/parameters/zfs_arc_max and #echo 2147483648 > /sys/module/zfs/parameters/zfs_arc_min if you want fixed ARC size. I use /etc/rc.local for custom tuning the system.at startup.

You know ashift is immutable so Proxmox is not invented nothing with it. edit: This named blocks is more closer to VM filesystem block naming.

No point. It will effect only single fs/volume with no effecting children data`s

You made some mistakes. If you want to change VM ID you need. 1. Turn off VM. 2. Rename VM config file. 3. Change VM disks location ( in ZFS rename ) 4. Change config disk location inside VM config file. 5. Start VM p.s. why a lot of people do server restart? Do you use windows or what?

Why reboot? This setting activate online.

Change the strategy of backup. Use bareos inside VM to do increment backups.