So you're not really sure it's the ARC growing, but only that the kernel
is growing
to 6.8GB.
Print the arc values via mdb:
# mdb -k
Loading modules: [ unix krtld genunix specfs dtrace uppc scsi_vhci ufs
ip hook neti sctp arp usba nca lofs zfs random sppp crypto ptm ipc ]
arc::print -t
Hi.
How a user-defined property can be removed? I can't find a way...
--
Pawel Jakub Dawidek http://www.wheel.pl
[EMAIL PROTECTED] http://www.FreeBSD.org
FreeBSD committer Am I Evil? Yes, I Am!
pgpUfHYws9m6z.pgp
You should be able to get rid of it with 'zfs inherit'. It's not
exactly intuitive, but it matches the native property behavior. If you
have any advice for improving documentation, plese let us know.
- Eric
On Sun, Apr 01, 2007 at 08:25:39PM +0200, Pawel Jakub Dawidek wrote:
Hi.
How a
On Sun, Apr 01, 2007 at 12:03:36PM -0700, Eric Schrock wrote:
You should be able to get rid of it with 'zfs inherit'. It's not
exactly intuitive, but it matches the native property behavior. If you
have any advice for improving documentation, plese let us know.
Indeed, but I was more looking
This can't be done due to the way ZFS property inheritance works in the
DSL. You can explicitly set it to the empty string, but you can't unset
the property alltogether. This is exactly why the 'zfs get -s local'
option exists, so you can find only locally-set properties.
- Eric
On Sun, Apr
On Sun, Apr 01, 2007 at 02:20:29PM -0700, Eric Schrock wrote:
This can't be done due to the way ZFS property inheritance works in the
DSL. You can explicitly set it to the empty string, but you can't unset
the property alltogether. This is exactly why the 'zfs get -s local'
option exists, so
All file systems provide writes by default which are
atomic with respect to readers of the file. That's a
POSIX requirement.
Surely, only in the absence of a crash - otherwise, POSIX would require
implementation of transactional write semantics in all file systems.
- bill
This message
