[Tux3] Design note: Data flush and rename ordering

[Daniel Phillips]

On Tuesday 24 March 2009, Thomas Bellman wrote:
> Daniel Phillips wrote:
> 
> > This additional requirement for rename is unlikely to reduce write
> > performance perceptably, because write/rename loads are relatively
> > rare.
> [...]
> > Mass file writes such as cp -a or
> > untar do not typically use the write/rename method.
> 
> cp -a and untar might not, but rsync does.  Thus, mass write/renames
> are probably not *that* rare.  For instance, Gentoo uses rsync to
> download its portage tree, and there are lots of small files in that.
> And at my workplace we and our users often move large file trees
> (several gigabytes or even terabytes) between fileservers using rsync.

Isn't rsync one of those applications where you want to be sure you
have either the old or the new version of a file, and not something
in between or empty?

Regards,

Daniel

_______________________________________________
Tux3 mailing list
Tux3 at tux3.org
http://mailman.tux3.org/cgi-bin/mailman/listinfo/tux3