JBD: barrier-based sync failed on dm-0:8 disabling barriers

[Florent]

I get such message in the boot log. I don't know what it means.

root@jaunty# dmesg |grep barrier
[ 4.649648] EXT4-fs: barriers enabled
[ 42.046266] EXT4-fs: barriers enabled
[ 47.338573] JBD: barrier-based sync failed on dm-0:8 - disabling barriers

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
NonfreeKernelModules: ath_hal
Package: linux-image-2.6.28-9-generic 2.6.28-9.29
ProcCmdLine: root=UUID=9ceb4b9e-7677-4031-a6da-1996e3542ca2 ro vga=789 quiet
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-9.29-generic
SourcePackage: linux

[Florent (florent.x)]

So it seems to be minor issue.
http://www.novell.com/support/search.do?cmd=displayKC&sliceId=SAL_Public&externalId=3907838
I've added option "barrier=0" on the line in /etc/fstab to silent the error.

What is strange is that I have 2 partitions mounted as EXT4.
 * The first one is on sda2 and is mounted with barriers enabled
 * The second is on dm-1 (luks encrypted partition) and gives the above problem

Maybe there's some interference with LUKS feature.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Simon Déziel (sdeziel)]

I am also affected by this bug. I have a KVM guest that runs Lucid on a virtio drive and I get the following message :

Nov 17 20:03:39 vpn01 kernel: [ 3.672378] JBD: barrier-based sync failed on vda1-8 - disabling barriers

The file associated to the virtio device lives on a RAID-0 MD device.

[Alexey Maximov (amax)]

any news about fixing this bug?

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Simon Déziel (sdeziel)]

I can't re-open this but but it should be as this also affects Lucid. See my comment in #5.

[LGB [Gábor Lénárt] (lgb)]

I have this problem on lucid (on amd64). I don't know if it counts but system was installed as jaunty, and after the usual upgrade process between that and lucid, I see now this error in the kernel log. However I have no idea if it's dangerous or not. Does it cause performance regression? Just because the filesystem I/O seems to be slower, but it's just a feeling.

[LGB [Gábor Lénárt] (lgb)]

Sorry, I forgot to tell, that the exact message is this (maybe it's not the very same ...):

[ 11.689308] JBD: barrier-based sync failed on cciss!c0d0p1-8 - disabling barriers
[ 16.199104] JBD: barrier-based sync failed on cciss!c0d0p3-8 - disabling barriers

[Karsten W. Rohrbach (byteborg)]

In the KVM case define your backing store as non-cached:

    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source dev='/dev/XXX'/>
      <target dev='vda' bus='virtio'/>
    </disk>