Hi,

On 20 Jun 2008, at 07:23, Matthew Dillon wrote:

quoted text
> [...] I will be making one final media change on Friday and then  
> HAMMER
>    development will go into testing & bug fixing mode until the  
> release.
>    This last media change will fix mtime and atime storage.  At the  
> moment
>    mtime/atime updates require generating UNDO records and, needless  
> to say,
>    they're expensive.  I will consider my options tomorrow but I  
> think I
>    am going to just not include those fields in the CRC so they can be
>    updated asynchronously, without any UNDO's. [etc]


That's harmless for atime, but you really want mtime to be properly  
synchronised with the last data update (and to stay that way across an  
undo). Ideally, timestamp data records and hold mtime as a reference  
to the last one updated (or something like that).

--
Bob Bishop          +44 (0)118 940 1243
rb@gid.co.uk fax +44 (0)118 940 1295