Hello eric, Friday, April 20, 2007, 3:36:20 PM, you wrote:
>> >> Has an analysis of most common storage system been done on how they >> treat SYNC_NV bit and if any additional tweaking is needed? Would such >> analysis be publicly available? >> ek> I am not aware of any analysis and would love to see it done (i'm ek> sure any vendors who are lurking on this list that support the ek> SYNC_NV would surely want to speak up now). ek> Due to not every vendor not supporting SYNC_NV, our solution is to ek> first see if SYNC_NV is supported and if not, then provide a config ek> file (as a short term necessity) that you can hardcore certain ek> products to act as if they support SYNC_NV (which we would then not ek> send a flushing of the cache). If the SYNC_NV bit is not supported ek> and the config file is not updated for the device, then we do what we ek> do today. ek> But if anyone knows for certain if a particular device supports ek> SYNC_NV, please post... Why config file and not a property for a pool? Ahhhh.... pool can have disks from different arrays :) Useful thing would be to ba able to keep that config file in a pool so if one exports/imports to different server... you get the idea. -- Best regards, Robert mailto:[EMAIL PROTECTED] http://milek.blogspot.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
