Skip to contentSkip to conversation

reiserfs - difference between a commit and a transaction

DISCUSSION Micha Feigin 2 participants 3 messages Feb 6, 2004

lore
Share & tools
lore
#0 lore raw

I am trying to do some work on reiserfs to make it laptop-mode compliant. After looking at the code because it was still noisy after I thought I told correctly to be quite, raised a question that I was hoping someone can clarify for me.

Reiserfs has both a transaction and a commit and I was wondering what is which.

(I am mostly interested in this from the point of what max_trans_age and max_commit_age affect)

Thanks

#1 lore raw
Quoted 7 lines · Micha Feigin

I am trying to do some work on reiserfs to make it laptop-mode compliant. After looking at the code because it was still noisy after I thought I told correctly to be quite, raised a question that I was hoping someone can clarify for me.

Reiserfs has both a transaction and a commit and I was wondering what is which.

Transaction is a sequence of file system modifications that (by the virtue of file system implementation) is bound to either be completed as a whole or be aborted as a whole (this is called "atomicity").

Commit is a certain operation performed during transaction life-time to implement its atomicity.

Quoted 3 lines

(I am mostly interested in this from the point of what max_trans_age and max_commit_age affect)

Take a look at the "commit" mount option of reiserfs.

Quoted 2 lines

Thanks

Nikita.

#2 lore raw
Quoted 9 lines · Nikita Danilov
Quoted 7 lines · Micha Feigin

I am trying to do some work on reiserfs to make it laptop-mode compliant. After looking at the code because it was still noisy after I thought I told correctly to be quite, raised a question that I was hoping someone can clarify for me.

Reiserfs has both a transaction and a commit and I was wondering what is which.

Quoted 7 lines

Transaction is a sequence of file system modifications that (by the virtue of file system implementation) is bound to either be completed as a whole or be aborted as a whole (this is called "atomicity").

Commit is a certain operation performed during transaction life-time to implement its atomicity.

So, at what time of a transaction's life would a commit be flushed to disk, only in the process of flushing the transaction to disk or at several points during its life time to make sure that atomicity is preserved.

And on that note, can there be several transactions active at one time or is a new transaction created only when the previous is closed and ready to flush.

Quoted 6 lines
Quoted 3 lines

(I am mostly interested in this from the point of what max_trans_age and max_commit_age affect)

Take a look at the "commit" mount option of reiserfs.

Thats what I was looking at and what I ported to 2.4 (it did require a fix for laptop mode to enable reseting the value, but that will be coming shortly).

The problem was that reiserfs was still being very noisy (kreiserfsd was writing to disk around every 30 seconds despite beeing mounted with commit=600). That led me to look further into the code and changing max_trans_age instead of max_commit_age kept it quite for the full ten minutes. I am still checking to make sure that its not something with me or my system.

For laptop mode we want to keep disk activity quiet for around ten minutes at a time so that the disk can be spun down, thus sacrificing the chance of loosing data for battery life.

I am trying to see what is the right value to change and what is the meaning of changing it but I could only find old documentation and the comments in the code are good only for people who know the meaning of the terms in the first place.

Quoted 10 lines
Quoted 2 lines

Thanks

Nikita.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/