I'm using faubakup for a daily backup of large partitions containing
over 100000 files.
I understand that there is a directory ..inodes that gets created that
will hold informations on backups... which tends to fill my inode table
on the ext3 partition where I save the backups.
Thus, if faubackup tends to be using many more inodes than any "normal"
use of an ext2/3 filesystem would expect, I think it could be wise to
warn the users somehow... or correct that in order, for instance, to use
some kind of database for the administrative data of the tools instead
of directories and files ?
I'm gonna try with a reiserfs partition now, to solve the problem of
inodes saturation, since it seems to correct this problem.
I found no mention of that issue in the docs nor on this list.
Has anyone had the same problem ?
Is there any other turnaround ?
Thanks in advance.
P.S.: I'm not subscribed to the list, so please cc: me in any followup.
Olivier BERGER <olivier.berger@...>
Ing=E9nieur Recherche - Dept INF
INT Evry (http://www.int-evry.fr)
On Fri, Jun 11, 2004 at 01:56:12PM +0200, Olivier Berger wrote:
> I'm using faubakup for a daily backup of large partitions containing
> over 100000 files.
> I understand that there is a directory ..inodes that gets created that
> will hold informations on backups... which tends to fill my inode table
> on the ext3 partition where I save the backups.
well, the directory only contains hardlinks to the files that are
contained in the backup. So these inodes will be shared and the
only new inodes are those that are needed for the directories.
Perhaps you should try playing with the -i parameter of mke2fs
if you have problems with your backup.
But choosing a file system without an inode limit may indeed be better.
Good luck for your backups! :)