From af6115579c870a648424d6ad44810f38459f2193 Mon Sep 17 00:00:00 2001
From: Bruce Dubbs <bdubbs@linuxfromscratch.org>
Date: Sun, 17 May 2009 02:52:18 +0000
Subject: Add an explanation about using the barrier option in fstab. Fixes
 #2318.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@8881 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
---
 chapter08/fstab.xml | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

(limited to 'chapter08/fstab.xml')

diff --git a/chapter08/fstab.xml b/chapter08/fstab.xml
index 026ec000c..2bf2cb2ad 100644
--- a/chapter08/fstab.xml
+++ b/chapter08/fstab.xml
@@ -95,4 +95,19 @@ EOF</userinput></screen>
   <!-- Personally, I find it more foolproof to always specify the iocharset and
   codepage in /etc/fstab for MS-based filesystems - Alexander E. Patrakov -->
 
+  <para>It is possible to make the ext3 filesystem reliable across power
+  failures for some hard disk types.  To do this, add the
+  <option>barrier=1</option> mount option to the appropriate entry in
+  <filename>/etc/fstab</filename>.  To check if the disk drive supports
+  this option, run 
+  <ulink url="http://www.linuxfromscratch.org/blfs/view/cvs/general/hdparm.html">hdparm</ulink>
+  on the applicable disk drive.  For example, if:</para>
+
+<screen><userinput>hdparm -I /dev/sda | grep NCQ</userinput></screen>
+
+  <para>returns non-empty output, the option is supported.</para>
+
+  <para>Note: Logical Volume Management (LVM) based partitions cannot use the
+  <option>barrier</option> option.</para>
+
 </sect1>
-- 
cgit v1.2.3-54-g00ecf