Todd E. Moore wrote:
> I'm working with a group that wants to commit all the way to disk
> every single write - flushing or bypassing all the caches each time.
> The fsync() call will flush the ZIL. As for the disk's cache, if
> given the entire disk, ZFS enables its cache by default. Rather
Carson Gaspar wrote:
> Todd E. Moore wrote:
>> I'm working with a group that wants to commit all the way to disk every
>> single write - flushing or bypassing all the caches each time. The
>> fsync() call will flush the ZIL. As for the disk's cache, if given the
>> entire disk, ZFS enables its ca
Todd E. Moore wrote:
> I'm working with a group that wants to commit all the way to disk every
> single write - flushing or bypassing all the caches each time. The
> fsync() call will flush the ZIL. As for the disk's cache, if given the
> entire disk, ZFS enables its cache by default. Rather than Z
I'm working with a group that wants to commit all
the way to disk every single write - flushing or bypassing all the
caches each time. The fsync() call will flush the ZIL. As for the
disk's cache, if given the entire disk, ZFS enables its cache by
default. Rather than ZFS having to issue the
Todd E. Moore wrote:
>
> I want to disable write cache on the disk drives in our J4200 JBODs so
> that fsync() actually writes to disk, not just to the cache on the drive.
>
ZFS will do this for you, via the way the ZIL works.
Neil explains it pretty well at
http://blogs.sun.com/perrin/entry/the_
I
want to disable write cache on the disk drives in our J4200 JBODs so
that fsync() actually writes to disk, not just to the cache on the
drive.
I did
this using 'format -e', but it displays a warning about the drive being
part of a zpool and also it says that the change is not permanent.