I have a large (1.5TB) partition with millions of files on it. e2fsck has been running nearly 12 hours and is still on "Checking directory structure". Any tips for speeding this along? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20100831/8653d551/attachment-0002.html>
On Tue, Aug 31, 2010 at 08:14:23AM -0500, Sean Carolan wrote:> I have a large (1.5TB) partition with millions of files on it. e2fsck has > been running nearly 12 hours and is still on "Checking directory structure". > Any tips for speeding this along?Yes -- use ext4. Otherwise, it's inevitable. -- Matthew Miller mattdm at mattdm.org <http://mattdm.org/>
On Aug 31, 2010, at 9:14 AM, Sean Carolan <scarolan at gmail.com> wrote:> I have a large (1.5TB) partition with millions of files on it. e2fsck has been running nearly 12 hours and is still on "Checking directory structure". Any tips for speeding this along?Disable fsck for that file system then google for online/delayed/background fsck script. The script will take an LVM snapshot and fsck the snapshot and only if it finds a problem with the snapshot will it email the operator and set the file system to be fsck'ed on the next reboot. When it finishes it deletes the snapshot. This will allow your system to come up right away. Performance will decline during this, but it's better than inaccessible. -Ross
On Tue, Aug 31, 2010 at 8:49 AM, Brent L. Bates <blbates at vigyan.com> wrote:> ? ? Use the XFS file system and never have to worry about fsck again. ?You'll > have a fast, more reliable, and more robust file system with over a decade and > exabytes of use under its belt that you will never have to wait for fsck > again.When this server gets rebuilt this is probably the path we will take. Thanks for the tip.
Sean Carolan wrote:> I have a large (1.5TB) partition with millions of files on it. e2fsck has > been running nearly 12 hours and is still on "Checking directory > structure". > Any tips for speeding this along?Kill it. And make sure it doesn't try to do it. There's a known bug with fsck (at least I think it was with CentOS, not *bleah* FC13). On large drives that we're doing online backups, it hits 70% and that's all she wrote: it never ends, and I need to kill it. mark