victorhooi
Contributor
- Joined
- Mar 16, 2012
- Messages
- 184
Hi,
I have a:
The Bhyve instance is backed by a 300 GB ZVOL (with 32 KB ZVOL block size), formatted as ext4.
I've read that COW (copy-on-write) filesystems have poor performance with BitTorrent. And that apparently turning on pre-allocation on your Bittorrent client will not help.
My question is - if I use the torrent client to write directly to the ZVOL - will that affect other ZFS datasets within the same ZFS pool? Or will it somehow isolate the "damage" (fragmentation?) that the torrent client causes to just that ZVOL?
The plan was to use the ZVOL as a scratchdisk - have the torrent client download the files to that, and then when complete, copy it from the Docker container straight to another ZFS data-set on the same host machine (via CIFS).
Any other caveats/considerations I should be wary of here?
Thanks,
Victor
I have a:
- FreeNAS 11 instance with
- 6 x 8TB WD spinning disks
- Running in RAID-Z1.
- Serving CIFS clients via Gigabit Ethernet/Wifi.
The Bhyve instance is backed by a 300 GB ZVOL (with 32 KB ZVOL block size), formatted as ext4.
I've read that COW (copy-on-write) filesystems have poor performance with BitTorrent. And that apparently turning on pre-allocation on your Bittorrent client will not help.
My question is - if I use the torrent client to write directly to the ZVOL - will that affect other ZFS datasets within the same ZFS pool? Or will it somehow isolate the "damage" (fragmentation?) that the torrent client causes to just that ZVOL?
The plan was to use the ZVOL as a scratchdisk - have the torrent client download the files to that, and then when complete, copy it from the Docker container straight to another ZFS data-set on the same host machine (via CIFS).
Any other caveats/considerations I should be wary of here?
Thanks,
Victor