On Friday 03 August 2007, Junio C Hamano wrote: > David Kastrup <dak@xxxxxxx> writes: > > > Junio C Hamano <gitster@xxxxxxxxx> writes: > > > >> * With -l, as long as the source repository is healthy, it is > >> very likely that the recipient would be, too. Also it is > >> very cheap. You do not get any back-up benefit. > > > > Oh, but one does: an overzealous prune or rm -oopswrongoption in one > > repo does not hurt the other. > > That's not "back-up" benefit I was thinking about. It is more > about protecting your data from hardware failure. If one is serious about backing up ones repo to protect it from hardware failure, there is not much use at all in cloning (by copy, hardlink, or otherwise) to a different location on the _same_ filesystem. In order for a backup to be at least marginally useful, it should be on a different disk drive (which you hint at below), or even better; on a different continent... My point is as follows: One has to clone a repo onto (at least) a different filesystem if one is serious about backup. But if one is cloning to a different filesystem, hardlinking is no longer an option; git _has_ to make a copy of some sort. Therefore we might as well hardlink as long as we're on a single filesystem (since the extra copy would not be worth much, backup-wise). > You physically have bits in two places, preferrably on separate disk > drives. > And that is what you do not get from hardlinked clone. If the two copies are on separate disk drives (i.e. separate filesystems), you cannot make a hardlink in the first place. If the two copies are on the same filesystem, they're not much more worth than a single copy (backup-wise). Given the clone-to-same-filesystem(-with-hardlink-capability) scenario (which is the only scenario where we have the option of using hardlinks), we have the following pros and cons when using hardlinks instead of copying: Pros: - Hardlink is _much_ faster (for big repos, we're talking orders of magnitude faster) Cons: - Hardlink will not leave two copies on the disk. But I'm arguing that the additional copy will have pretty much _no_ value from a redundancy POV, since the copy is still left on the _same_ filesystem. Some would even go as far as to say that the second copy provides a false sense of security as long as it is located on the same filesystem. Have fun! ...Johan -- Johan Herland, <johan@xxxxxxxxxxx> www.herland.net - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
