On Mon, Dec 19, 2011 at 12:40 AM, Jan-Aage Frydenbø-Bruvoll <j...@architechs.eu> wrote: > Hi, > > On Sun, Dec 18, 2011 at 16:41, Fajar A. Nugraha <w...@fajar.net> wrote: >> Is the pool over 80% full? Do you have dedup enabled (even if it was >> turned off later, see "zpool history")? > > The pool stands at 86%, but that has not changed in any way that > corresponds chronologically with the sudden drop in performance on the > pool.
>From http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide (or at least Google's cache of it, since it seems to be inaccessible now: " Keep pool space under 80% utilization to maintain pool performance. Currently, pool performance can degrade when a pool is very full and file systems are updated frequently, such as on a busy mail server. Full pools might cause a performance penalty, but no other issues. If the primary workload is immutable files (write once, never remove), then you can keep a pool in the 95-96% utilization range. Keep in mind that even with mostly static content in the 95-96% range, write, read, and resilvering performance might suffer. " I'm guessing that your nearly-full disk, combined with your usage performance, is the cause of slow down. Try freeing up some space (e.g. make it about 75% full), just tot be sure. -- Fajar _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
