Date: Tue, 8 May 2012 16:31:28 -0500 (CDT) From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us> To: Michael Gmelin <freebsd@grem.de> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS resilvering strangles IO Message-ID: <alpine.GSO.2.01.1205081625470.9406@freddy.simplesystems.org> In-Reply-To: <180B72CE-B285-4702-B16D-0714AA07022C@grem.de> References: <73F8D020-04F3-44B2-97D4-F08E3B253C32@grem.de> <CAFHbX1K0--P-Sh0QdLszEs0V1ocWoe6Jp_SY9H%2BVJd1AQw2XKA@mail.gmail.com> <180B72CE-B285-4702-B16D-0714AA07022C@grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 8 May 2012, Michael Gmelin wrote: > > Do you think it would make sense to try to play with zfs_resilver_delay directly in the ZFS kernel module? This may be the wrong approach if the issue is really that there are too many I/Os queued for the device. Finding a tunable which reduces the maximum number of I/Os queued for a disk device may help reduce write latencies by limiting the backlog. On my Solaris 10 system, I accomplished this via a tunable in /etc/system: set zfs:zfs_vdev_max_pending = 5 What is the equivalent for FreeBSD? Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.2.01.1205081625470.9406>