Skip to contentSkip to conversation

ext4: Clarify impact of 'commit' mount option

PATCH Applied Jan Kara 2 participants 2 messages Dec 18, 2019 – Dec 22, 2019 Documentation

lore
Share & tools
lore

Jan Kara

author
#0 lore raw

PATCH 1/1 ext4: Clarify impact of 'commit' mount option

The description of 'commit' mount option dates back to ext3 times. Update the description to match current meaning for ext4.

---
 Documentation/admin-guide/ext4.rst | 19 +++++++++++--------
 1 file changed, 11 insertions(+), 8 deletions(-)
Documentation/admin-guide/ext4.rst +11 -8
index 059ddcbe769d..8d292f5aaea3 100644
@@ -181,14 +181,17 @@ When mounting an ext4 filesystem, the following option are accepted:
         system after its metadata has been committed to the journal.
 
   commit=nrsec	(*)
-        Ext4 can be told to sync all its data and metadata every 'nrsec'
-        seconds. The default value is 5 seconds.  This means that if you lose
-        your power, you will lose as much as the latest 5 seconds of work (your
-        filesystem will not be damaged though, thanks to the journaling).  This
-        default value (or any low value) will hurt performance, but it's good
-        for data-safety.  Setting it to 0 will have the same effect as leaving
-        it at the default (5 seconds).  Setting it to very large values will
-        improve performance.
+	This setting limits the maximum age of the running transaction to
+	'nrsec' seconds.  The default value is 5 seconds.  This means that if
+	you lose your power, you will lose as much as the latest 5 seconds of
+	metadata changes (your filesystem will not be damaged though, thanks
+	to the journaling). This default value (or any low value) will hurt
+	performance, but it's good for data-safety.  Setting it to 0 will have
+	the same effect as leaving it at the default (5 seconds).  Setting it
+	to very large values will improve performance.  Note that due to
+	delayed allocation even older data can be lost on power failure since
+        writeback of those data begins only after time set in
+        /proc/sys/vm/dirty_expire_centisecs.  
 
   barrier=<0|1(*)>, barrier(*), nobarrier
         This enables/disables the use of write barriers in the jbd code.
Signature · 1 line
2.16.4