disk check at boot up time

[Basil Chupin]

On 05/02/12 18:19, Jonas Norlander wrote:
> 2012/2/5 Basil Chupin<blchupin at iinet.net.au>:
>> On 05/02/12 07:33, ray burke wrote:
>>> can anyone help?
>>>
>>> I have been told to insert "sudo touch /forcefsck" in a terminal
>>> window when log into
>>> Â k10.10mm so as to force
>>> a disk check at next boot time of which I have done, but every time I
>>> boot up now is does
>>> the fsck, and I only want it to do it once, so what is the command to do
>>> this?
>>>
>>> ray
> "sudo rm /forcefsck" removes the file and should stop the file system
> check at boot unless there is something wrong with your file system so
> its marked dirty.
>
>> Why are you worried about it?
>>
>> A quick fsck is done everytime you boot to make sure that there has been no
>> corruption to your file sysem (assuming here that you have used ext3 or ext4
>> when you installed). And there is a more comprehensive fsck done after every
>> (?)20 boots of the system.
>>
>> BC
> If I understand it right, when using a journaling file system it will
> not be checked unless its marked dirty by the kernel, a check is
> forced by /forcefsck, max-mount-count or interval-between-checks has
> been reach.
>
> You can check the current values max-mount-count and
> interval-between-checks with "sudo tune2fs -l /dev/sda1". Replace sda1
> with your partition to check.
>
> See "man tune2fs" for more info and how to fine tune the file system
> and when a check is forced.

Question: does it matter or not if the file sysem is quicly checked on 
each boot?

Yes or No?

BC

-- 
A three-year-old boy was examining his testicles while taking a bath.
"Mum" he asked, "are these my brains?"
"Not yet," she replied.