With latest Nevada setting zfs_arc_max in /etc/system is
sufficient. Playing with mdb on a live system is more
tricky and is what caused the problem here.
-r
[EMAIL PROTECTED] writes:
> Jim Mauro wrote:
>
> > All righty...I set c_max to 512MB, c to 512MB, and p to 256MB...
> >
> > > arc::print -tad
> > {
> > ...
> > ffffffffc02e29e8 uint64_t size = 0t299008
> > ffffffffc02e29f0 uint64_t p = 0t16588228608
> > ffffffffc02e29f8 uint64_t c = 0t33176457216
> > ffffffffc02e2a00 uint64_t c_min = 0t1070318720
> > ffffffffc02e2a08 uint64_t c_max = 0t33176457216
> > ...
> > }
> > > ffffffffc02e2a08 /Z 0x20000000
> > arc+0x48: 0x7b9789000 = 0x20000000
> > > ffffffffc02e29f8 /Z 0x20000000
> > arc+0x38: 0x7b9789000 = 0x20000000
> > > ffffffffc02e29f0 /Z 0x10000000
> > arc+0x30: 0x3dcbc4800 = 0x10000000
> > > arc::print -tad
> > {
> > ...
> > ffffffffc02e29e8 uint64_t size = 0t299008
> > ffffffffc02e29f0 uint64_t p = 0t268435456 <------ p
> > is 256MB
> > ffffffffc02e29f8 uint64_t c = 0t536870912 <------ c
> > is 512MB
> > ffffffffc02e2a00 uint64_t c_min = 0t1070318720
> > ffffffffc02e2a08 uint64_t c_max = 0t536870912 <------- c_max is
> > 512MB
> > ...
> > }
> >
> > After a few runs of the workload ...
> >
> > > arc::print -d size
> > size = 0t536788992
> > >
> >
> >
> > Ah - looks like we're out of the woods. The ARC remains clamped at 512MB.
>
>
> Is there a way to set these fields using /etc/system?
> Or does this require a new or modified init script to
> run and do the above with each boot?
>
> Darren
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
