What if there *are* serious file-system problems? We're half-way into CPU hour 7 of our e2fsck run on a 8TB OST with ~274 million inodes:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND ##### root 25 0 15.1g 1.1g 772 R 100 57.4 472:07.67 e2fsck If it finishes within my lifetime I'll post how long it takes. Thanks, Adam On Wed, 2009-07-29 at 04:35 -0600, Andreas Dilger wrote: > On Jul 29, 2009 15:16 +0800, huangql wrote: > > We want to run e2fsck on OSTs to finish them. However, as to the > > running time, we should estimate how long it takes to run e2fsck on > > OSTs. We hopefully to know what elements to affect the running time like > > the size of OST, the average size of files and so on. Can you give us > > the tips for it? And I hope to receive you email as soon as possible. > > The variables in your question are numerous: > - size of the filesystem > - number of inodes > - number of allocated blocks > - distribution of the above on the disk > - speed of the disks > - speed of the CPU > - amount of RAM on server > > Reasonable e2fsck times (without serious filesystem problems) might > take between 5 minutes and 2 hours. > > Cheers, Andreas > -- > Andreas Dilger > Sr. Staff Engineer, Lustre Group > Sun Microsystems of Canada, Inc. > > _______________________________________________ > Lustre-discuss mailing list > [email protected] > http://lists.lustre.org/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
