Good idea. Provides options, but it would be nice to be able to set a
low water mark on what can be taken away from the arc metadata cache
without having to have something like an SSD.
Dave
On 10/01/10 14:02, Freddie Cash wrote:
On Fri, Oct 1, 2010 at 11:46 AM, David Blasingame Oracle
<david.blasing...@oracle.com> wrote:
I'm working on this scenario in which file system activity appears to cause
the arc cache to evict meta data. I would like to have a preference to keep
the metadata in cache over ZFS File Data
What I've notice on import of a zpool the arc_meta_used goes up
significantly. ZFS meta data operations usually run pretty good. However
over time with IO Operations the cache get's evicted and arc_no_grow get
set.
<snip>
So, I would like to limit the amount of ZFS File Data that can be used and
keep the arc cache warm with metadata. Any suggestions?
Would adding a cache device (L2ARC) and setting primarycache=metadata
and secondarycache=all on the root dataset do what you need?
That way ARC is used strictly for metadata, and L2ARC is used for metadata+data.
--
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
