zfs instantly makes the buffered copy older

[Margaret]

I finally got fed up with having files scattered around auto-decaying and built up a FreeBSD fileserver to centralise them, using zfs scrubbing to auto-protect against auto-decay.

But I now have a weird problem!  Every time I save off the file I'm working on, zfs snatches it up and scrutinises it to update its crc.   But that makes the copy in the editor (v9.0) "older" than the one on disk, which prompts  a prompt:  "are you silly enough to want to replace the newer, shinier file on disk with this older, grotty one?" (okay, not quite that wording, but the sentiment's accurate.  Fsvo accurate) 

I don't want to auto-update the file in the buffer because of having had files stepped on and then auto reloaded in their crumbled state.

Is there some other simple solution?  Surely one of the thousands of people who adopted zfs years ago had this problem and solved it to keep themselves from being driven mad.

[Dennis]

I do not remember if v9.0 had this, but under File Options > Auto reload, there is an option to "Compare file contents before auto reload".  With this enabled, SlickEdit would detect that even though the modification date of the file changed, the actual file contents had not changed, and it would not prompt to auto-reload.

[Margaret]

Saddeningly, v9 doesn't have it.