On Jul 24, 2009, at 16:00, Miles Nordin wrote:
Is there a correct way to configure it, or will always any
componoent of the overall system other than ZFS get blamed when ZFS
loses a pool?
By default VB does not respect the 'disk sync' command that a guest OS
could send--it's just ignored. This messes up ZFS' assumption about
transaction being safely on-disk.
Toby Thain posted a link to a VB forum posting on how to configure
things so that the flush command is not silently ignored:
http://forums.virtualbox.org/viewtopic.php?f=8&t=13661&start=0
ZFS doesn't make many assumptions, but it does assume that when the
disk says "the data is safe" it actually is. If the disk lies then
this is where things go wonky (and why we have these giant threads).
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
