On 12/20/2011 4:51 PM, Istvan Gabor wrote:
2011. december 20. 21:46 napon Anton Aylward
írta: Istvan Gabor said the following on 12/20/2011 01:59 PM:
At every Nth mount fsck checks a given partition, which takes a long time.
fsck is¬* linear with the size of a file system but a function of the power (square) or the size.
So a 4G FS will take longer to process than two 2G FS. Also the 2 file systems will be able to the fsck'd in parallel :-) You might also consider a setup where the 2 FS are _not_ fsck'd together: both have the same N but are spaced apart by M.
Thank you all for your responses.
From the answers it seems I haven't explained clearly what I wanted. I don't have any problem with file system checking at boot, I think it is good. Therefore I don't want to change the change max-mount-counts (number).
My problem is that occasionally I do not have the time to wait until fsck stops checking even one partition (eg is takes 5 minutes but I need to use the system within a minute). As I am not following the partitions' mount counts I don't know in advance whether a partition will be checked or not, when I start the system. When I see that fsck already started to check the filesystem I'd like to press a button (eg escape) which signals to the system that I want to cancel or interrupt checking and continue with the next step in the boot process. Is it possible? If not, it should be implemented.
Thomas, is the 'fastboot' option you mentioned related to the "doing fast boot" message shown at the beginning of boot?
Thanks,
Istvan
I think your best option is to: * make sure all large fs's are journaling (reiserfs, ext4, etc) * drastically increase or disable altogether the periodic boot time scanning (not disabling the fsk if the fs is found to be dirty at boot) * manually fsck once in a while if you like. Because you can't predict when you will want to boot and run as fast as possible, and those times are _exactly_ the times you _don't_ want to have to futz with special boot prompt parameters. You could also make a menu.lst stanza that just has fastboot added to it. That way you could boot up fast without having to stop and enter special boot prompt options. Just select the fastboot entry instead of the regular entry. fsck does process interrupt signals gracefully. You could possibly modify the initrc or other boot script to allow a break signal (ctrl-c) to reach the fsck process (it's probably trapped by a trap command before fsck runs normally, but you could edit the script with another trap command that releases that trap just before fsck). And aborting a read-only checkup fsck should always be safe. But aborting fsck at all is just a really unwise habit to give yourself. So I would do one of the other things that avoids running fsck in the first place. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org