> >Quoth Darren Dunham on Wed, Aug 15, 2007 at 12:50:33PM -0700: > >> But a traditional filesystem isn't going to write anything without a > >> request. ZFS is constantly updating the pool/uberblock status the way > >> things currently work. So even if you choose to defer the atime update > >> until much longer, it won't prevent writes from being scheduled anyway. > > > >Why does ZFS update the uberblock when there are no writes? > > It doesn't. I have a ZFS filesystem on an IDE disk which has an idle > timer set; when there's no ZFS I/O there's also no disk I/O and the > disk spins down.
I've incorrectly understood the flush algorithm. So then delaying or deferring the writes should work as well. In fact, if those are the only writes, then you'll defer an entire label write/head seek sequence, which would likely be heavier weight than a simple inode update (and give you a bigger win). -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
