blkid takes 2 hours to complete on RHEL 5.5

Solution Verified - Updated -

Issue

  • blkid takes an exceptionally long time to run when a large number of device mapper devices are present in a system and/or the blkid.tab file is fairly large.

Environment

  • Red Hat Enterprise Linux 5.5 or prior
    • e2fsprogs version < e2fsprogs-1.39-27.el5
  • A large number (100's or more) of blkid recognizable devices

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.