helprdiff-backup - Support: sr #102559, possible impractical: sparse files


sr #102559: possible impractical: sparse files

Submitted by:  Invalid User ID <#24737>
Submitted on:  Tue 28 Oct 2003 11:06:22 AM UTC  
Category:  None Priority:  5 - Normal
Severity:  2 - Minor Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Operating System:  None

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Mon 26 Sep 2005 09:24:00 AM UTC, comment #1: 

On a FC4 x86_64 system my /var/log/lastlog file had grown to 1.2TB. As /var/log/lastlog is a sparse file this is not really problem for FC4, but rdiff-backup seems to not support sparse files so this poses a problem for the backup.

My current workaround is to exclude /var/log/lastlog from the backup, but I do lose historic information by doing this. It would be nice if rdiff-backup would support sparse files.

As to the x86_64 platform I think the offsets used for lastlog have been increased or something. I have seen the same problem om 32-bit systems before, the impact however was much smaller. Typically this involves backuping up a file several (tens of) MB's in size. This is dooable, but backing up several GB's or even TB's is a whole different story...



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


CC list is empty


Do you think this task is very important?
If so, you can add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.




No changes have been made to this item

Back to the top

Powered by Savane 3.5