Taken from http://www.ussg.iu.edu/hypermail/linux/kernel/0405.3/0669.html: > > The idea here is > > that a filesystem can tag an IO request as a barrier and the disk will not > > reorder writes across the barrier. It provides additional integrity > > guarantees for the journalling filesystems. The feature is enabled for > > reiserfs and ext3.
What you are seeing is an informative message, not an error. Don't worry about it. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Wu Sent: Thursday, June 30, 2005 10:20 AM To: [email protected] Subject: DMESG output Hi Listserv, Can anyone tell me why I am getting these messages, what they mean and how to get rid of them : JBD: barrier-based sync failed on dm-5 - disabling barriers JBD: barrier-based sync failed on dm-2 - disabling barriers out of order segment: rcv_next 8EE939AE seq 8EE939C7 - 8EE939C8 ofo requeuing : rcv_next 8EE939C7 seq 8EE939C7 - 8EE939C8 out of order segment: rcv_next 9051F084 seq 9051F09D - 9051F09E ofo requeuing : rcv_next 9051F09D seq 9051F09D - 9051F09E out of order segment: rcv_next 90556FBF seq 90557087 - 90557088 ofo requeuing : rcv_next 90557087 seq 90557087 - 90557088 TIA Bernie Wu [EMAIL PROTECTED] ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
