On 12/11/09 14:56, Bill Sommerfeld wrote:
On Fri, 2009-12-11 at 13:49 -0500, Miles Nordin wrote:
"sh" == Seth Heeren <s...@zfs-fuse.net> writes:
sh> If you don't want/need log or cache, disable these? You might
sh> want to run your ZIL (slog) on ramdisk.
seems quite silly. why would you do that instead of just disabling
the ZIL? I guess it would give you a way to disable it pool-wide
instead of system-wide.
A per-filesystem ZIL knob would be awesome.
for what it's worth, there's already a per-filesystem ZIL knob: the
"logbias" property. It can be set either to "latency" or
"throughput".
That's a bit different. logbias controls whether the intent log block blocks
go to main pool or the log devices (if they exist). I think Miles
was requesting a per fs knob to disable writing any log blocks.
A proposal for this exists that suggests a new sync property: everything
synchrnous; everything not synchronous (ie zil disabled on fs); and the
current behaviour (the default). The RFE is:
6280630 zil synchronicity
My problem with implementing this is that people might actually use it!
Well actually my concern is more that it will be misused.
Neil.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
