Why do I see "kernel: JBD: barrier-based sync failed on dm-0 - disabling barriers" messages on Red Hat Enterprise Linux?

Solution Verified - Updated -

Issue

  • I get "kernel: JBD: barrier-based sync failed on dm-0 - disabling barriers" messages when I use "barrier=1" option on a file system in a logical volume, why?
  • We've been seeing some barrier-based sync failed on one of our servers after recent kernel upgrade (to 2.6.18-238.12.1.el5): 
    kernel: JBD: barrier-based sync failed on dm-1-8 - disabling barriers
kernel: JBD: barrier-based sync failed on dm-0-8 - disabling barriers
kernel: JBD: barrier-based sync failed on dm-2-8 - disabling barriers
kernel: JBD: barrier-based sync failed on dm-5-8 - disabling barriers
kernel: JBD: barrier-based sync failed on dm-6-8 - disabling barriers
kernel: JBD: barrier-based sync failed on dm-4-8 - disabling barriers

Environment

  • Red Hat Enterprise Linux 5
  • ext3 filesystems mounted with "barrier=1" option
  • ext4 filesystems mounted with "barrier=1" or "default" mount options.
    • barrier=1 is a default mount option for ext4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content