Carlos F. Lange wrote:
Anyone else getting annoyed by the periodic check forced in ext3 partitions?
No. It's a good thing. In the old days, going back to Unix, fsck was performed on every file system on EVERY boot up. If it weren't for periodic forced checks, you would never be fscking your filesystems at all, until some corruption becomes so bad that: 1) you notice it and 2) it's frustratingly difficult, if not impossible to repair without data loss.
I started using ext3 in my large /home partitions, as recommended by openSUSE (still using Reiser for my smaller RAID1 root partition, because of this strange bug: https://bugzilla.novell.com/show_bug.cgi?id=350992 ) and today I passed again the 60 days limit without checking ext3 and I had to wait 10 minutes for the 200GB partition to be checked.
It is bad enough that we don't get any decent feedback in the splash
When the splash screen comes up, hit the Escape (Esc) key, and you'll get all the feedback you want.
screen ( https://bugzilla.novell.com/show_bug.cgi?id=344271 ), which I
It's not a bug.
can imagine is unsettling to many new users, who will have no clue about what is happening.
What I really question is if these lengthy checks are really needed.
If you don't want to know about filesystem corruption until it's past the point of repaiting, then I guess you don't need them.
My Reiser partition was cleared with a simple journal check (isn't that what journaling systems are about?). Add to that the fact that hard disks are becoming bigger and these forced check times can mean one might need to wait 20 minutes or 1/2 hour to get access to the machine again? Obviously this will happen when you have to leave in 10 minutes and you are just about to print out that vital document and your foot hits the reset switch...
What is the use of investing a lot of effort into reducing the boot time by precious seconds to give users a better Linux experience, if you have to wait 10 minutes for fsck every time you boot (since Linux
Fsck is happening EVERY time you boot? Why are you doing improper shut-downs so that each of the filesystems is marked as "dirty"
allows you to run several months without reboot, until the next kernel patch comes by).
It finds and corrects filesystem corruption while the damage is still painlessly repairable.
There, I vented...
How often do you reboot? akulkis@kulkix:~> uptime 4:43pm up 11 days 18:25, 83 users, load average: 4.15, 3.42, 1.75 akulkis@kulkix:~> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org