Why root is remounted with commit=0 (=600 specified in fstab) at the end of start-up?
My problem is that in fstab I have specified commit=600 but during start-up
something remounts root with commit=0 option. Here is the log: Code:
% dmesg | grep sdd1 | grep re- If somebody have an idea why this is happening and how can I stop this, please help me. If not, at least some clues how to find what script/program is doing this would be appreciated. I'm using fresh (less than 2 weeks old) installation of Debian GNU/Linux Testing and KDE. I know I can remount it manually or write startup script that remounts it one more time, but I want to find the source of the problem and fix it. |
Found it: /usr/lib/pm-utils/power.d/journal-commit
This script is responsible for the problem. To solve, I removed "commit=600" from fstab and changed variable for "commit" option when on AC power in the script. I do not need it on my workstation (working 24/7) but KDE requires pm-utils so I cannot purge it. I'm really surprised by the fact that everywhere everybody says to put "commit" option in fstab where it does have ZERO effect if you have KDE (and therefore pm-utils) installed. And I did not find anything in any manual about necessity to edit "journal-commit" script if I'm not happy with default "commit=0". Hopefully information in this topic will be useful to somebody. |
Editing /usr/lib/pm-utils/power.d/journal-commit is not necessary (and bad idea because upgrade can overwrite it with new version). Using "commit" option in /etc/fstab is bad idea too. So how to do it properly? After some research I think that putting these lines in /etc/sysctl.d/local.conf is the solution:
Code:
vm.dirty_writeback_centisecs = 60000 |
All times are GMT -5. The time now is 02:47 PM. |