On Tuesday 12 December 2006 19:29, Oliver Lehmann wrote: > Georg Altmann wrote: > > > The solution proposed is to keep file flags in a list and set them after > > all files have been restored, so that all hardlinks can be created. Though > > it is probably enough to do this for hardlinked files. Looks like this > > would make the restore code even more complicated. > > > > But what is the solution if you restore a file from an incremental backup > > which is a hardlink to an IMMUTABLE file? > > Or what is when you just try to restore the hardlink (and you didn't knew > it was a hardlink). Beside saying that reinstalling the OS should be > recommended here, the IMMUTABLE flag can also be used for non-OS files > too. This can't be "fixed" by just reinstalling the OS ;)
> I'd say that > keeping the flags and setting them when the whole restore is done is one > step in the right direction and fixes at least some of the problems. Even > if it does not fix the problems 100% It is *very* unlikely I will implement any linked list for exactly the reasons that I stated in my previous email. It seems that either I don't write very clearly or you guys are just not reading what I wrote. By the way, when restoring a file, Bacula does know whether or not it is a hardlink. If the OS permits Bacula to remove the immutable bit, then it would be possible to remove the immutable bit before hardlinking a file, and then put it back, and this without keeping any lists. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
