This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new!

mkfs and mount options

Posted by: Anonymous [ip:] on July 02, 2008 07:25 AM
"Journaling filesystems can use write barriers to protect their journaled metadata. If you are using a hardware card to provide RAID functionality, these barriers might force the entire cache on the RAID card and all disks assembled into the RAID on that card to be synced, which can lead to extremely poor performance. As a real-world example, an Adaptec 31205 12-port card with a RAID-6 and XFS using barriers can support less than 100 file creates per second in tests I recently performed. Explicitly disabling barriers in XFS when mounting the same filesystem gives closer to 6,000 file creates per second. Though I'm not advocating disabling barriers in XFS, in this particular hardware configuration it could be done without data loss risk."

ext3 has not used write barriers; IIRC the devs are just now exploring the utility of write barriers, and determining how to schedule them.

As far as XFS, you may also check out the "-l lazy-count=1" option to mkfs.xfs. From the man page:

"This changes the method of logging various persistent counters in the superblock. Under metadata intensive workloads, these counters are updated and logged frequently enough that the superblock updates become a serialisation point in the filesystem. The value can be either 0 or 1.

"With lazy-count=1, the superblock is not modified or logged on every change of the persistent counters. Instead, enough information is kept in other parts of the filesystem to be able to maintain the persistent counter values without needed to keep them in the superblock. This gives significant improvements in performance on some configurations. The default value is 0 (off) so you must specify lazy-count=1 if you want to make use of this feature."


Return to Using Bonnie++ for filesystem performance benchmarking