Benutzer-Werkzeuge

Webseiten-Werkzeuge


voyage_on_alix

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen gezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
voyage_on_alix [2013/05/12 18:09]
scytheman [Mode Switch Button]
voyage_on_alix [2014/03/01 17:13] (aktuell)
Zeile 65: Zeile 65:
 Note 1: By combining write cycles and reducing their interval you increase the risk of loosing data on crashes or power failure (here: up to 10min of work). Additionally,​ memory usage increases. Note 1: By combining write cycles and reducing their interval you increase the risk of loosing data on crashes or power failure (here: up to 10min of work). Additionally,​ memory usage increases.
  
-Note 2: You can monitor application'​s write operations by executing ''​echo 1 > /​proc/​sys/​vm/​block_dump''​ and watching the output of ''​dmesg''​ or ''/​var/​log/​syslog''​.+Note 2: You can monitor application'​s ​read and write operations by executing ''​echo 1 > /​proc/​sys/​vm/​block_dump''​ and watching the output of ''​dmesg''​ or ''/​var/​log/​syslog''​. ''​echo 0 > /​proc/​sys/​vm/​block_dump''​ disables the logging again.
  
 Note 3: Activating the kernel'​s laptop mode by setting ///​proc/​sys/​vm/​laptop_mode//​ to a value >0 should have no effect for flash drives as they don't need to be spun down. As the kernel documentation says: "When the knob is set, any physical disk I/O (that might have caused the hard disk to spin up) causes Linux to flush all dirty blocks. The result of this is that after a disk has spun down, it will not be spun up anymore to write dirty blocks, because those blocks had already been written immediately after the most recent read operation."​ Note 3: Activating the kernel'​s laptop mode by setting ///​proc/​sys/​vm/​laptop_mode//​ to a value >0 should have no effect for flash drives as they don't need to be spun down. As the kernel documentation says: "When the knob is set, any physical disk I/O (that might have caused the hard disk to spin up) causes Linux to flush all dirty blocks. The result of this is that after a disk has spun down, it will not be spun up anymore to write dirty blocks, because those blocks had already been written immediately after the most recent read operation."​
voyage_on_alix.txt · Zuletzt geändert: 2014/03/01 17:13 (Externe Bearbeitung)