> So the question is whether the ".bdar" file is specific to the filesystem > being backed up, and if it only allows backing up the whole filesystem? > Does it create a dense output file or a sparse one? Does it store the > data as chunks of blocks in a full-device map or on a per file basis? Let's see.. yes, yes, dense, full-device. It's a tiny little program, you could read it in 10 minutes :). You'll giggle at how incomplete its knowledge of ext* is. > If you can't restore a .bdar backup file to a smaller device than the > source device that makes it less useful than most of the other tools. It is different in a way that won't satisfy people who want to restore to smaller devices, yes. > The question is whether the 2x speed improvement is worth the lack of > portability compared to even dump? Indeed. For me, in my current situation, it is. - z -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
