Because of the default settings in SQL Server (for the model database), and a lack of understanding about how the transaction log should be sized and maintained, I run into many databases that have a high number of virtual log files inside the transaction log file.
Even though I have written about this before, a recent incident has prompted me to reiterate some of the great content that is available on this subject.
The gist of all of this is that you should check the number of VLFs on each of your databases, and if they are over about 50, take the easy steps needed to reduce them. Then, based on your business requirements and log generation rate, manually grow your log file to an appropriate size to avoid having auto-grow kick in during normal operation (including index maintenance). I always leave auto-grow enabled as a safety measure, but with the growth increment set to an explicit size in MB.