Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Mar 2012 16:35:00 -0600 (CST)
From:      Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
To:        Dan Rue <drue@therub.org>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: ZFS and mdconfig -t vnode - Unexpected behavior
Message-ID:  <alpine.GSO.2.01.1203081630510.27785@freddy.simplesystems.org>
In-Reply-To: <20120308161940.GA71851@therub.org>
References:  <20120308161940.GA71851@therub.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 8 Mar 2012, Dan Rue wrote:
>
> Under ZFS, it can take as long as 30 seconds before the block size as
> reported by du -k has been updated. The fsync appears to be a noop.

Zfs under Solaris has the same behavior.  This data is only assured to 
be available after the current zfs TXG has been synced, which may take 
a long time.  It also becomes available after the 'sync' system call 
has completed (because the current TXG is flushed).

> Are there any ZFS tunables that could be related to this? What could be
> the cause of this behavior?

You could adjust the tunings for zfs transaction groups but this will 
decrease system performance and increase pool fragmentation.

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.1203081630510.27785>