Am 23.10.2014 um 15:10 schrieb Anton Aylward:
On 10/23/2014 05:27 AM, Daniel Bauer wrote:
Is this normal? Should I check some settings?
Thanks for explanation or hints...
The short answer is that ReiserFS is a journaling file system. Journaling is a mechanism that helps file systems survive crashes.
Previously, file systems could not guarantee to have written both data and structure to the physical disk in the event of a crash.
This is a good analysis though rather technically abstract http://research.cs.wisc.edu/wind/Publications/sba-usenix05.pdf
caching, delayed write and other mechanisms speed the computer's performance, but a at a cost in the event of a disaster.
http://www.ibm.com/developerworks/library/l-journaling-filesystems/ ...
Also look at man tunefs.reiserfs
And of course http://en.wikipedia.org/wiki/Journaling_file_system
Also worth reading http://lwn.net/Articles/283161/ http://www.linuxjournal.com/article/4466
Uff, I don't want to get a file system specialist :-) But anyway, thanks a lot! The answer to my question was found on your link on the IBM site under ReiserFS: "The commit policy depends on the journal size but is based on the number of blocks to commit." This makes all clear to me. I thought it depended on time and idle states, but as it is size and numbers it's only logical that there may be a lot to commit even after a long time of doing nothing... Thanks and regards from Barcelona. Daniel -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com room in Barcelona: https://www.airbnb.es/rooms/2416137 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org