Search results

I got this Info from the ZFS Mailing-List: Then so be it. But again for the Question regarding "FSYNCS/SECOND": How can it be, that I have only a Value of ~500 with SSD and others have Values of a few thousand with HD's? ->...

I asked on the ZoL-Mailinglist and they have confirmed that TRIM is not supported yet. Used someone SSD's under ZoL?

Yes, i talk about ZFS. And yes, i tested with the same Values of ARC min/max. I do not understand why there is such a large Difference between Linux & FreeBSD.

no, not activated.

I still have made some more Speed Tests, between the Tests I always rebooted, so that nothing is cached: dd inside the Nas4Free VM (SATA Controller passed through): nas4free: ~ # dd if=/mnt/raid1-ssd/pve/images/110/vm-110-disk-1.qcow2 of=/dev/null bs=2M count=3000 3000+0 records in 3000+0...

Today i tested the newest available Version of Nas4Free "9.3.0.2 - Nayla (Revision 1349)" and there, the dd Speed-Test increased to >750MB/s :D root@proxmox:~# dd if=/mnt/pve/nas4free-ssd/images/110/vm-110-disk-1.qcow2 of=/dev/null bs=2M count=2000 2000+0 records in 2000+0 records out...

I know, but the Problem seems to be the Network.

But why is then the iperf-Test so good?

For a Fileserver Virtualization i passthrough a SATA Controller to a Nas4Free VM. There i have et al an mirrored ZFS SSD Pool (2 x Samsung 840 Pro). The Read-Performance from this Pool inside the Nas4Free VM is very fast: ~1GB/sec. The Dataset of this Pool I've shared via NFS and added in...

Ok, but what can exactly happen in worst case of a Crash? ZFS on the Host remains consistent. But what about the Guest VM's (Windows ntfs / Linux ext3/4), could the File Systems of the VMs be damaged or become inconsistent? Or is missing only the Part that was in the Cache?

http://pve.proxmox.com/wiki/ZFS http://forum.proxmox.com/threads/8829-Is-it-Cache-writeback-safe?p=49937#post49937 To use a Secure File System, I need to make an unsafe setting? Does not contradict that? What exactly can happen in the worst case?

I want to passthrough one of my two Onboard SATA-Controller's from Supermicro X10SAE Mainboard. When i start the VM, i get this message: With my Intel Mainboard DQ67SW this works fine without Errors. Is this a Hardware or Software (Kernel?) Problem?

As I've read, my Crucial-M4 has Garbage Collection, so it should be ok to use ZFS without TRIM.

Thanks. Do I Need "pve-qemu-kvm" or "qemu-server" or both?

My last trial would be to test the previous QEMU Version. Please can someone explain me how exactly i do that? Downgrade "pve-qemu-kvm" or "qemu-server" or both? And How exactly?

I do not understand what You want to tell me?

I would like to set up a new Proxmox 3.4 Server on a SSD. The new installer offers the possibility to use ZFS as Host-File-System. But here http://open-zfs.org/wiki/Features i have read, that ZoL has no TRIM Support!? Should I better use ext4?

KSM is enabled by default, see "/etc/default/ksmtuned" # Defaults for ksmtuned initscript # sourced by /etc/init.d/ksmtuned # installed at /etc/default/ksmtuned by the maintainer scripts # # This is a POSIX shell fragment # # start ksmtuned at boot [yes|no] START=yes I have tested your...

+1 agree too.

I checked a old Backup for "ksmtuned.conf", it's exact the same as now. Once more, is it possible that it is a QEMU Problem? And how can i Test the previous Version?