From cc0abef5bffc95b198175e00ad43d17bed02108b Mon Sep 17 00:00:00 2001 From: Stefan Hajnoczi Date: Wed, 28 Mar 2012 09:32:32 +0100 Subject: [PATCH] --- yaml --- r: 307917 b: refs/heads/master c: ee65244b210e00060c2d4d8eff4ad9b18400f588 h: refs/heads/master i: 307915: e34c2181ef1a60f8fbcc1752d559af9eeabce0ea v: v3 --- [refs] | 2 +- trunk/Documentation/filesystems/ext3.txt | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index edd0f0b736a0..fb6576b68223 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: ac0dd2474822fbd7d8e8cca12495e6b4760556cd +refs/heads/master: ee65244b210e00060c2d4d8eff4ad9b18400f588 diff --git a/trunk/Documentation/filesystems/ext3.txt b/trunk/Documentation/filesystems/ext3.txt index b100adc38adb..293855e95000 100644 --- a/trunk/Documentation/filesystems/ext3.txt +++ b/trunk/Documentation/filesystems/ext3.txt @@ -59,9 +59,9 @@ commit=nrsec (*) Ext3 can be told to sync all its data and metadata Setting it to very large values will improve performance. -barrier=<0(*)|1> This enables/disables the use of write barriers in -barrier the jbd code. barrier=0 disables, barrier=1 enables. -nobarrier (*) This also requires an IO stack which can support +barrier=<0|1(*)> This enables/disables the use of write barriers in +barrier (*) the jbd code. barrier=0 disables, barrier=1 enables. +nobarrier This also requires an IO stack which can support barriers, and if jbd gets an error on a barrier write, it will disable again with a warning. Write barriers enforce proper on-disk ordering