Opened 17 years ago

Closed 14 years ago

#13143 closed defect (fixed)

Hard-links used for image-mode don't really fit Time Machine

Reported by: spiralyoda-macports@… Owned by: macports-tickets@…
Priority: Low Milestone: MacPorts 2.0.0
Component: base Version: 1.5.0
Keywords: Cc: nerdling (Jeremy Lavergne)
Port:

Description

When doing a full restauration with leopard's time machine, I noticed a little downside with macports, because by default macports uses hardlinks for the files it installs, hardlink of /opt/local/var/software/* in /opt/local/*. As Time Machine already uses an external disk, and also uses hard links for its own internal "cooking", macports' hardlinks aren't kept as is, & when restauring we get 2 different files, though using more space in /opt/local & maybe would this also cause some problems if upgrading some ports, I don't know for sure.

Possible clues: using symlinks, disabling image mode, "deactivating and reactivating everything would recreate the hardlinks too I think", thanks to afb for the suggestion.

Change History (8)

comment:1 Changed 17 years ago by jmpalacios (Juan Manuel Palacios)

Milestone: MacPorts base bugs

comment:2 Changed 17 years ago by raimue (Rainer Müller)

This is rather a issue of Time Machine if it cannot backup hard links correctly.

comment:3 Changed 17 years ago by spiralyoda-macports@…

Well, of course it's an issue of Time Machine, but :

a) I don't think we have enought weight to make sure apple solves it so we'd better find a workaround in macports. b) The way hard-links work make it really difficult to store them on a different hard-drive (reference number for a file on a volume...) c) Time machine internally uses hard-links for incremental backups d) I don't think what is done with hard-links in macports couldn't be done as well with symlinks, and symlinks would perfectly fit with Time Machine.

comment:4 Changed 17 years ago by kballard (Lily Ballard)

Symlinks would probably break a lot of stuff.

comment:5 Changed 17 years ago by danielluke (Daniel J. Luke)

The initial implementation used symlinks (which mostly works but does break some things). In fact, the current implementation falls back to symlinks if hard links don't work.

An existing workaround is to just run in 'direct' mode (perhaps with 'archivemode' as well).

comment:6 Changed 16 years ago by tobypeterson

Milestone: MacPorts base bugsMacPorts Future

Milestone MacPorts base bugs deleted

comment:7 Changed 14 years ago by nerdling (Jeremy Lavergne)

Cc: snc@… added

Cc Me!

comment:8 Changed 14 years ago by jmroot (Joshua Root)

Milestone: MacPorts FutureMacPorts 2.0.0
Resolution: fixed
Status: newclosed

No longer using hardlinks as of r77511.

Note: See TracTickets for help on using tickets.