>> Dump reads from the raw device; restore writes through the
>> filesystem, and every file create involves a bunch of synchronous
>> writes..

> Uh, why?

Why which?

> What's wrong with a fs-neutral dump?

- it can't get holes completely right (at least not without writing to
  the files in question)

- it's significantly less efficient, because it perforce walks the
  filesystem in filesystem-tree order instead of inode order

- it can't help modifying atimes or ctimes

It does exist, though; it's called tar.

> Is restore fs-neutral?

Yes; restore runs atop the usual filesystem interface.  That's exactly
why it's so slow - it's doing lots of file creates, and each one
involves a synchronous write of a directory block and I think an inode
block as well.

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B