Christo Kutrovsky <kutrov...@pythian.com> writes: > Has anyone seen soft corruption in NTFS iSCSI ZVOLs after a power > loss?
this is not from experience, but I'll answer anyway. > I mean, there is no guarantee writes will be executed in order, so in > theory, one could corrupt it's NTFS file system. I think you have that guarantee, actually. the problem is that the Windows client will think that block N has been updated, since the iSCSI server told it it was commited to stable storage. however, when ZIL is disabled, that update may get lost during power loss. if block N contains, say, directory information, this could cause weird behaviour. it may look fine at first -- the problem won't appear until NTFS has thrown block N out of its cache and it needs to re-read it from the server. when the re-read stale data is combined with fresh data from RAM, it's panic time... > Would best practice be to rollback the last snapshot before making > those iSCSI available again? I think you need to reboot the client so that its RAM cache is cleared before any other writes are made. a rollback shouldn't be necessary. -- Kjetil T. Homme Redpill Linpro AS - Changing the game _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
