Search results

1. you can use top/free/htop INSIDE the container. No need to use it on host if you want to check the container. I know you can see processes from inside, but it is much helpful using the tools there. 2. So your SMB process is reaching ~900MB resident size after the transfer? Is it hard to post...

It does not show the host. It shows the used/free memory inside the container. (e.g. free command) I've also checked with htop and it shows the container used/limit memory, not the host. If the used memory is high inside the container use top and "shift-M" to sort by used memory. Again, I...

You need to gather more data from the console.

The RAM used for disk caching is released upon request. Where exactly do you check the RAM used?

Those are not settings. Those are header sizes in ARC if the data block is in: - ARC only - ARC and L2ARC - L2ARC only

Enable what modes? There have been multiple topics here. primary and secondary cache settings control what goes in ARC and L2ARC (nothing, metadata, metadata+data).

You can increase the L2 filling rate. There are some parameters.

root@hypervisor:~# uname -a Linux hypervisor 4.2.3-1-pve #1 SMP Wed Oct 21 14:40:52 CEST 2015 x86_64 GNU/Linux root@hypervisor:~# grep arc_max /etc/modprobe.d/zfs.conf options zfs zfs_resilver_delay=0 zfs_resilver_min_time_ms=5000 zfs_top_maxinflight=128 zfs_scrub_delay=0...

4.46% is peanuts. You get more with lz4 compression.

Forget about thin provision. It has nothing to do with dedup. You write a block with hash H1. If you write again a block that has the same hash (restore, new VM, whatever) it will simply put a link to the first block instead of writing the full block. So you want to have 8GB of RAM for: ARC...

zfs list -o name,compression,ratio

I don't remember exactly but it might be, yes. For me, the recovery of deleted blocks is more important. For example, it is very helpful when doing a full zfs send/receive.

You select "SCSI" as the disk type and then in "Options" tab you select VIRTIO as the SCSI controller type.

That is not ZIL I/O. It is normal I/O. If you use a slog then the writes to it will happen when they occur. That applies to writes without a slog, if they are sync writes. The 5 seconds flush is normal. If you see high I/O and throughput, maybe you need more drives. If you see high I/O and low...

And considering that 1TB of storage is cheaper than 5GB of RAM...

VIRTIO SCSI brings UNMAP (TRIM) support, so your zvols will shrink if you delete blocks inside the guest.

If both drives are corrupted that means the source of error is upstream. Like you say, either software (I say this is unlikely because lots of people could have issues if ZFS borks the checksums) or... memory? Even CPUs and/or their caches can be broken sometimes.

ZoL has lots of issues, not ZFS. You don't need to set the paramter. You can upgrade to latest PVE release (from test repo I think). It has 0.6.5.3.

I doubt mcelog will show you memory issues (I really don't know). You will be amazed, I run ECC memory and I get bits flipped from time to time, although a past memtest was fine. I also have 2 hard drives that show no error counters (0), but they've shown ZFS errors few times and one of them is...

Do you have ECC memory? SATA cables?