... something like this: set timestamp = `hammer now` cpdup /mountpoint/@@$timestamp targethost:/ ... into your filesystem. set timestamp = `hammer stamp 60s` <------ doesn't sync ... of replication), with both running HAMMER, but only retain a limited ...

dragonflybsd-kernel - Matthew Dillon - Mar 25 2008 - 01:26

... It's not really in the HAMMER design any more, primarily because HAMMER's volume model seems to work fine as-is. Ultimately something like ... would be treated as a separate project. HAMMER's redundancy model is going to be ...

dragonflybsd-kernel - Matthew Dillon - Mar 24 2008 - 17:00

... : Thomas E. Spanjaard : tgen@netphreax.net Making the 'hammer now' command do a sync() is a good idea. I ... we just created is still in the in-memory cache (HAMMER caches the raw records it intends to commit later on). ...

dragonflybsd-kernel - Matthew Dillon - Mar 24 2008 - 23:02

So is it needed to run hammer now in order to "create" a snapshot? What would I do in situation like this: got a hammer filesystem and couple of the files change on day to day basis. Then a week later I needed ...

dragonflybsd-kernel - Petr Janda - Mar 25 2008 - 00:16

> > And, as you know, fully coherent filesystem access across machines is > going to be the basis for DragonFly's clustering across said machines. > > In summary, things are progressing very well. > Hi Matt, That's good to know

dragonflybsd-kernel - Petr Janda - Mar 24 2008 - 10:38

Matthew Dillon wrote: > * Full historical access appears to be working but needs testing. > Note that a sync is still needed to flush dirty cached data prior > to acquiring a timestamp for the 'snapshot' to be set in stone. > (

dragonflybsd-kernel - Thomas E. Spanjaard - Mar 24 2008 - 21:19