Hot answers tagged

3

We were looking into running Mongo on ZFS and saw that this post raised major concerns about the performance available. Two years on we wanted to see how new releases of Mongo that use WiredTiger over mmap, performed on the now officially supported ZFS that comes with the latest Ubuntu Xenial release. In summary it was clear that ZFS doesn't perform quite ...


2

I think the problem with your -nv approach was that intermediate filesystems are not created when receiving with -n, and therefore it will fail every time, while it works without the no-op flag (but expanding the complete filesystems may take a long time). Unfortunately, most documentation/blogs online do not use this flag, therefore they never experience ...


2

I think this might just be a limitation of the way it works. To me it seems to just scan the snapshots for different versions of the current file, so won't show any versions if the file has been renamed. However I'm not sure what you mean by history being lost if you move a file to another directory. On my FreeBSD/Samba system I can view previous versions ...


1

I would suggest executing the script from the sending side and using that to trigger the receive portion. There's no sense in starting a cron job on both ends... You can issue commands on your remote server from the local server using ssh.


1

As of ZFS on Linux version 0.6.3, ACLs are now supported. To enable them, you must set the acltype dataset property to the value posixacl, e.g.: zfs set acltype=posixacl tank/home If you haven't already, you should also set xattr to sa: zfs set xattr=sa tank POSIX ACLs are stored as extended attributes. Unfortunately, the standard way of storing ...


1

Ended up asking on the ZFS-on-Linux mailing list, and eventually figured out that my problem was that the ZFS ARC was using too much of the system RAM (or more specifically, not leaving enough free). This was resulting in contention over memory between other Kernel tasks and ZFS, with the result that there was a lot of I/O on the system (non-ZFS) disk, and ...


1

What you described are Boot Environments (BE), which will be created automatically on system upgrades or manually with the beadm command. You can have multiple independent BEs, although only a single one can be active at the same time. You also can update/modify each BE separately. Normally you would do that to test specific software versions or a full ...


1

From the white paper from Adurant: The benefits of this configuration include: Reduced Hadoop cluster overhead by reducing the replication factor to 2x Reduced storage (disk space) requirements by reducing the replication factor to 2x Increased the number of copies of data to 4x via the ZFS Storage Appliance Added data compression via the ...



Only top voted, non community-wiki answers of a minimum length are eligible