Re: [Bug-xorriso] bug with handling symbolic links?

[Thomas Schmitt]

Hi,

>  -hardlinks "on" included in -for_backup was what I did not want -
> after I understood that this increases memory requirements quite noticeably.

Does it really have that much impact ?
Can you tell me how much memory both runs consume ?
(It's often hard to tell true virtual memory consumption
but real RAM consumption is quite a realistic indicator.)

Do you have lots of hard links in your snapshots ?
(It's only about inodes shared inside the directory
trees which you map into xorriso. It does not matter
whether there are other links pointing to those
inodes from outside those directories.)


> which was exceeded even with -temp_mem_limit 64k for some of the images.

The impact of -temp_mem_limit is restricted to higher
levels of xorriso, i fear. Things like pattern expansion
and file list sorting by block address.
If it works with setting 64k, then the memory consumption
is probably inside libisofs.


> The reason for setting -disk_dev_ino ino_only was for having the speed
> advantage

I was quite proud of that method when i developed it
for scdbackup a few years before i enterd the libburnia
adventure.
It has to deal with the counter-intuitive fact that
file timestamps do not change when the file gets
renamed or moved to a different directory. Imagine
two files swapping places.
(Then imagine my face when i learned about Samba's
inode dance.)


Have a nice day :)

Thomas