Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Should I use a CoW filesystem on my PC if I only wanted snapshot capabilities ? Post 303045038 by stomp on Wednesday 11th of March 2020 05:28:50 AM
Old 03-11-2020
Two more comments on zfs:
  • Don't fill up the filesystems
    If you fill up zfs file systems above 80%, performance will degrade.
  • No manual balancing method available
    If you have a Volume with more than one vdev and they are not equally full performance also degrades. For best performance vdev utilization should be equal of every vdev. But there are times when vdev utilization is completely different. For example if you add a new vdev: The new vdev will be empty. There are 2 typical ways to solve that:
    • utilization will slowly level to the pool average over time
      The percentage of the probability for a vdev to be the targe for a new write is the reversed percentage of the utilization of that vdev. So the least filled up vdev will get more new data as the other ones and the vdev utilization will average with writes and deletes over time.
    • export and import the zfs pool
      If you like to have it immediately, you may export and import the pool. That way on the import all data will be distributed evenly over all vdevs. That task of course needs a lot of temporary space and probably time when you have quite some TB of data.

Regarding the performance of filesystems, I'm interested in it quite much. Right now, I'm writing benchmark scripts testing different aspects of it and will open a thread here soon.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Capabilities?

We are looking into buying a new software, billing software that is, and want to know if you can run that on the same UNIX server as another major software? Is there a limit to the different types of software Unix can run, or is it like windows where you can install as many as you like? ... (2 Replies)
Discussion started by: hoz
2 Replies

2. UNIX for Advanced & Expert Users

p570 Capabilities

Hi there. I've been tasked with making a new design for our Unix systems :eek: Now the question I have is; How many LPARs can a p570 hold WITHOUT using a VIO Server. Many Thanks Kees (1 Reply)
Discussion started by: KeesH
1 Replies

3. Red Hat

Adding capabilities to an RPM

Hi. I downloaded a package that could only be installed on RHEL5, and not 4 or 3, so I got the source in order to compile it on RHEL 3 so hopefully it will work on all versions. So I have the source for a working package, but when I build it in RHEL 3 and then try to install it in RHEL 5, it... (6 Replies)
Discussion started by: Boaz
6 Replies

4. Filesystems, Disks and Memory

Wanted: Geographically distributed filesystem solution

I'm looking for a means to ensure that servers in the two or three datacenters, connected in a ring via IP through two ISPs, can distribute load and/or replicate data among at least two SAN-class disk devices. I want to evaluate several solutions, and I'm open to solutions ranging from free,... (6 Replies)
Discussion started by: otheus
6 Replies

5. Solaris

Cannot use filesystem while sending a snapshot

I've got a Solaris 11 Express installed on my machine. I have created a raidz2 zpool named shares and a simple one-disc zpool named backup. I have made a script that would send a daily snapshot of shares to backup. I use these commands zfs snapshot shares@DDMMRRRRHHMM zfs send -i shares@....... (10 Replies)
Discussion started by: RychnD
10 Replies

6. UNIX for Advanced & Expert Users

Use of Capabilities

I wonder if anyone could assist with some problems I'm having with Linux Capabilities and their use when using the commands "nice" and "schedtool". I run a couple of PCs, one is an elderly AMD Sempron 2800+ (32-bit, 2GHz clock and 3GB memory) that is used as a family multimedia system running... (3 Replies)
Discussion started by: MikeGM
3 Replies

7. Linux

Broadcom under Fedora 18 (Spherical Cow)

So I'm having a problem getting a Broadcom BCM4312 wireless controller to work under the broadcom-wl module $uname Linux 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux lspci -v 05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g... (2 Replies)
Discussion started by: Skrynesaver
2 Replies

8. UNIX for Advanced & Expert Users

Linux capabilities discussion

Hi I'm trying to compile my linux kernel with CONFIG_SECURITY_CAPABILITIES=y. any idea what this thing does ?? Also another question , If I compile the kernel that I'm currently using , what'll happen ? ~cheers (3 Replies)
Discussion started by: leghorn
3 Replies

9. What is on Your Mind?

Anybody want to talk about Dirty Cow?

Hi All, How worried is everyone about the Dirty Cow Linux exploit? Has anybody experienced attacks yet? From the research I've done it seems that the exploit is "reliable" (that is it works nearly every time on vulverable systems) which is not good news. We all believe that Unix/Linux... (3 Replies)
Discussion started by: hicksd8
3 Replies
ZFS-FUSE(8)							  [FIXME: manual]						       ZFS-FUSE(8)

NAME
zfs-fuse - ZFS filesystem daemon SYNOPSIS
zfs-fuse [--pidfile filename] [--no-daemon] [--no-kstat-mount] [--disable-block-cache] [--disable-page-cache] [--fuse-attr-timeout SECONDS] [--fuse-entry-timeout SECONDS] [--log-uberblocks] [--max-arc-size MB] [--fuse-mount-options OPT,OPT,OPT...] [--min-uberblock-txg MIN] [--stack-size=size] [--enable-xattr] [--help] DESCRIPTION
This manual page documents briefly the zfs-fuse command. zfs-fuse is a daemon which provides support for the ZFS filesystem, via fuse. Ordinarily this daemon will be invoked from system boot scripts. OPTIONS
This program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included below. For a complete description, see the Info files. -h --help Show summary of options. -p filename --pidfile filename Write the daemon's PID to filename after daemonizing. Ignored if --no-daemon is passed. filename should be a fully-qualified path. -n --no-daemon Stay in foreground, don't daemonize. --no-kstat-mount Do not mount kstats in /zfs-kstat --disable-block-cache Enable direct I/O for disk operations. Completely disables caching reads and writes in the kernel block cache. Breaks mmap() in ZFS datasets too. --disable-page-cache Disable the page cache for files residing within ZFS filesystems. Not recommended as it slows down I/O operations considerably. -a SECONDS --fuse-attr-timeout SECONDS Sets timeout for caching FUSE attributes in kernel. Defaults to 0.0. Higher values give a 40% performance boost. -e SECONDS --fuse-entry-timeout SECONDS Sets timeout for caching FUSE entries in kernel. Defaults to 0.0. Higher values give a 10000% performance boost but cause file permission checking security issues. --log-uberblocks Logs uberblocks of any mounted filesystem to syslog -m MB --max-arc-size MB Forces the maximum ARC size (in megabytes). Range: 16 to 16384. -o OPT... --fuse-mount-options OPT,OPT,OPT... Sets FUSE mount options for all filesystems. Format: comma-separated string of characters. -u MIN --min-uberblock-txg MIN Skips uberblocks with a TXG < MIN when mounting any fs -v MB --vdev-cache-size MB adjust the size of the vdev cache. Default : 10 --zfs-prefetch-disable Disable the high level prefetch cache in zfs. This thing can eat up to 150 Mb of ram, maybe more --stack-size=size Limit the stack size of threads (in kb). default : no limit (8 Mb for linux) -x --enable-xattr Enable support for extended attributes. Not generally recommended because it currently has a significant performance penalty for many small IOPS -h --help Show this usage summary. REMARKS ON PRECEDENCE
Note that the parameters passed on the command line take precedence over those supplied through /etc/zfs/zfsrc. BUGS
/CAVEATS The path to the configuration file (/etc/zfs/zfsrc) cannot at this time be configured. Most existing packages suggest settings can be set at the top of their init script. These get frequently overridden by a (distribution specific) /etc/default/zfs-fuse file, if it exists. Be sure to look at these places if you want your changes to options to take effect. The /etc/zfs/zfsrc is going to be the recommended approach in the future. So, packagers, please refrain from passing commandline parameters within the initscript (except for --pid-file). SEE ALSO
zfs (8), zpool (8), zdb(8), zstreamdump(8), /etc/zfs/zfsrc AUTHOR
This manual page was written by Bryan Donlan bdonlan@gmail.com for the Debian(TM) system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 any later version published by the Free Software Foundation, or the Common Development and Distribution License. Revised by Seth Heeren zfs-fuse@sehe.nl On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL. The text of the Common Development and Distribution Licence may be found at /usr/share/doc/zfs-fuse/copyright COPYRIGHT
Copyright (C) 2010 Bryan Donlan [FIXME: source] 2010-06-09 ZFS-FUSE(8)
All times are GMT -4. The time now is 06:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy