SearchFAQMemberlist Log in
Reply to topic Page 2 of 2
Goto page Previous  1, 2
Large backup taking far too long
Author Message
Post Large backup taking far too long 
i'm not the original poster, but i work with him:

Reiserfs allocates inodes dynamically, so they're spread all over the
filesystem. So, doing a 'ls -l' in a directory causes major head-seeking.
Other filesystems, including XFS apparently, group inodes together on the
disk. I would assume this solves the problem at the expense of the
filesystem having a fixed number of inodes after creation.

I'm going to give xfs a shot. I'll post my results.

Out of curiosity: how much RAM do you have? Linux 2.2 kernels used

the box has 256M.

to have an inode-max setting. I'm not sure if it is completely
dynamic in 2.4+ or if there is some other way to control the
cache size.

and i presume you think it should be larger, not smaller, correct? Smile

paul
=---------------------
paul fox, pgf < at > foxharp.boston.ma.us (arlington, ma, where it's 67.6 degrees)


-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Post Large backup taking far too long 
On Wed, 2004-06-09 at 06:45, Paul Fox wrote:

Out of curiosity: how much RAM do you have? Linux 2.2 kernels used

the box has 256M.

to have an inode-max setting. I'm not sure if it is completely
dynamic in 2.4+ or if there is some other way to control the
cache size.

and i presume you think it should be larger, not smaller, correct? Smile

Yes, it seems pretty obvious that if it is a problem to do
a long disk seek to read each inode, the solution is to
already have it cached in RAM. What does
sysctl fs.inode-state
return? The first 2 numbers should be the maximum slots for
caching inodes and the number currently cached. Mine
says 381009 193241 this morning with BackupPC_nightly
still running. Hmmm - even the 1st number seems to be
dynamic. Now it is 383293.

---
Les Mikesell
les < at > futuresource.com




-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Display posts from previous:
Reply to topic Page 2 of 2
Goto page Previous  1, 2
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB