Yes, I guessed the same way to solve it. My point is more about style of unpredictability. Nobody presumably likes when software does not what is expected AND without any explanations or messages to consider. Kinda ignoring a person behind keybord, isn't it?
Thank you for clarification.
I'd love some verbosity on the command, kind of "can't really remove it, it is necessary. but you may leave it disabled in peace, though" :)
And a descriptory comment in /etc/pve/storage.cfg to give a hint to leave it alone.
I have installed PVE 7.2-1 from iso, and had some minor experiments with CentOS7 in LXC, which I've learned can't really work inside modern host system. It can't be a reason for crippling host system I think.
I noticed unconvenient storage layout, and decided move storage local to /rpool/data...
yes, this wunderpiece works with 2.6.32-46-pve
kern.log:
kernel: nvme 0000:0c:00.0: PCI INT A -> GSI 26 (level, low) -> IRQ 26
kernel: nvme 0000:0c:00.0: setting latency timer to 64
kernel: IRQ 26/nvme0q0: IRQF_DISABLED is not guaranteed on shared IRQs
# ls -l /dev/nvme0*
crw------- 1 root...
I'm considering purchase of
SSD INTEL DC P3600 SSDPEDME800G401 800GB, PCI-E AIC (add-in-card), PCI-E x4
Does anybody know if this piece of wonder does work correctly in ProxmoxVE 3.4 or 4.2??
Does it give speeds close to as announced
read up to 2600 MB/s, write up to 1000 MB/s
?
Hi Henry,
I've successfully converted msw 2k8r2 server this way:
1) make backup internally with VHDX-image
2) qemu-img convert VHDX-image into QCOW2-image
3) create VM with ide first, then attach qcow2-image and later with virtio drivers as in wiki.
during convert it's possible to use "compact"...
# sync && echo 3 > /proc/sys/vm/drop_caches && dd if=/mnt/ssdata/images/202/vm-202-disk-1.qcow2 of=/mnt/ssdata/test.file bs=1M count=1024 conv=fdatasync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 16.2512 s, 66.1 MB/s
is that more realistic?
then it's awfull for SSD...
changed mount options wirthout discard, nightly backup completed in 6:54 vs 7:52 usually. users didn't noticed any difference.
added to cron to run fstrim daily in the early morning and output number of trimmed bytes to log file.
after a while I'll check it :)
that screenshot is of editing properties of a user account.
you want to receive scheduled backup notifications, from proxmox itself, so sender email address should be edited in
"Datacenter" choosen in left column and "Options" tab, field "Email from address", by default root@$hostname
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.