Paul Fox wrote:
>
> I don't see why not. Just change the hardlink into a file whose
> contents are the name of the pool file it pointed to. That seems like
> trival one liner in a script, both converting and unconverting the
> link. Since it seems too easy, there must be a "gotcha" which I am
> missing!
the gotcha i'm aware of comes at cleanup time -- right now, when
the last pc referencing a pool file stops needing the file, the
file in the pool is deleted during cleanup based on the link count
being equal to 1 (since that means there are no references to it).
changing from hard links would become more complicated and less
robust, since you'd either have to have another "who's using this
pool file" list, or you'd have to search all of the pc trees to look
for references, either at cleanup time, or at deletion time.
paul
=---------------------
paul fox, [EMAIL PROTECTED] (arlington, ma, where it's 24.1 degrees)
I may have misunderstood the original poster's intentions then, but I
thought he was proposing a way to bypass hardlinks whilst transferring
the pool to another site. In the event of disaster, (or as I
proposed, as soon as the pool is duplicated on the second site) you
may replicate the hardlinks by reversing the process by which the hash
values were saved in the pc files/hardlinks.
I had rather expected any "gotchas" to be in the time required for
relinking the pc files to the pool, or in intermediate disk space or
RAM usage.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
