Tag Info

Hot answers tagged

2

As tegbains pointed out in a comment, zfs send streams do not benefit from any storage-level deduplication in place. They also don't benefit from any other settings; this is why zfs send | zfs receive can be used to migrate data to new settings that otherwise would only take effect once the data is rewritten -- such a enabling or disabling deduplication, or ...


2

Do not do this. I repeat: Do not do this! You will get cluster headaches out of this. If metadata changes in meantime, it could cause crashes and/or invalid data returned. These filesystems are not designed to work like this. Do not use them that way. This is especially bad idea with ZFS. If you really have to, use something very very basic, without ...


1

I read on the freebsd forums a post which suggested to use zfs online -e <pool> <vdev> (without needing to offline the vdev first) This ultimately was the solution, but it required that ZFS autoexpand be disabled first: [root@timestandstill ~]# zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT dfbackup 214G 207G ...


1

Use one or the other. I suggest using /etc/exports for consistency and readability, especially if your NFS server is serving data from non-ZFS filesystems.


1

I suspect the ATA driver is retrying the read operation a couple of times when it receives an error before passing the error back to the filesystem driver. What this means is by the time the ZFS filesystem driver gets the result of the read the data is all there, and correct, but it likely took a bit longer than normal to happen. There is of course no error ...



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