Re: Re: Perfomance problem backupscript (more details and tests)

[email protected] wrote:

> Hi,
>
> > It is probably very common now to use usb drives (both flash
> > and real) and swap among systems.  I'd expect synthetic inode
> > numbers to change if the contents are modified between mounts.
>
> Another risk could be changing device numbers due
> to automagical hardware detection.
> I'm waiting for the first bug reports to come in.

So you should switch to Solaris. Solaris does nothave this problem
because there is a device instance database.

/etc/path_to_inst


> A lot of "changed" files. Righteously.
> My concern is more about situations which appear stable
> to the user. Like mounting a filesystem and finding
> all inode numbers hashed to new values.

In this case, you need to make a bug report to the fs driver
implementation maintainer.



> If it's multiple user's data, then Rockridge extensions may help.
> Alternatively a setfacl list works wonders.

Star supports ACLs since 4 years now...


> Therefore i have to test with afio and star.
> (Although i would be very astonished if a star level=0
> backup would not restore all hard links as they were.)

Of course it does!

What problems do you have?



> The hardlink detection and restoring problem looks quite
> expensive in terms of computing time and memory. At least
> if there are lots of such shared inodes.

Star does not need much time to detect and achive hard links.

If you have many of them, star will need a lot of memory....

Jörg

-- 
 EMail:[email protected] (home) Jörg Schilling D-13353 Berlin
       [email protected]		(uni)  
       [email protected]	(work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily