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

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

On 4 Feb 2012, at 20: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?
>

touch simply creates an empty file, so I would assume

sudo rm /forcefsk

would do the trick, but better wait for an authoritative answer before you try this.

Mark

> ray
>
> --
> kubuntu-users mailing list
> kubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users


--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

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


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

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


--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

On Sun, Feb 5, 2012 at 10:01 AM, Basil Chupin <blchupin@iinet.net.au> wrote:
> 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
>
>
> 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
>
> --
> A three-year-old boy was examining his testicles while taking a bath.
> "Mum" he asked, "are these my brains?"
> "Not yet," she replied.
>
>
>
> --
> kubuntu-users mailing list
> kubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

Basil,

I agree with every 20 or so restarts but get a little annoying when it
happens every boot?

ray

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

On 05/02/12 11:03, ray burke wrote:

On Sun, Feb 5, 2012 at 10:01 AM, Basil Chupin<blchupin@iinet.net.au> wrote:

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


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

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



--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

Basil,

I agree with every 20 or so restarts but get a little annoying when it
happens every boot?


And why not? Mine is checked at each boot. I have my home encrypted and
so see the messages on the screen up to the point where I am asked for
the passphrase to enter the home directory. If you look at your
/var/log/dmesg log you will see the same.


Don't forget that Linux is designed to be booted and allowed to run
24/7/365/n-years so when you switch your system off at night the system
thinks that there was a reason why it had to be "re-booted" and
therefore does a quick check. And if you keep doing it every night for
19 times on the 20th the system thinks, "Gosh, things ARE bad and I had
better do a proper file system check".


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.



--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

2012/2/5 Basil Chupin <blchupin@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.

/ Jonas

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

On 05/02/12 18:19, Jonas Norlander wrote:

2012/2/5 Basil Chupin<blchupin@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.



--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

Basil,


There is no "yes or no" answer possible.


In a perfect world it wouldn't matter. Unfortunately minor errors in writing to disk will happen. Even though it's extremely rare, compared to the billions of bytes written, even one altered bit can trash a whole file or programme. Fortunately most errors can be corrected if caught quickly before they can start a cascade of consequent errors. That is what fsck is there to do.



Now you could probably go for years without getting caught by this kind of disk corruption, but... wouldn't it be nice to have as much free and fast "insurance" as the wit of clever programmers can devise?



I thought so. Now you have your answer.




Sent from my Motorola Xoom Android tablet

On Feb 5, 2012 5:30 AM, "Basil Chupin" <blchupin@iinet.net.au> wrote:
On 05/02/12 18:19, Jonas Norlander wrote:


2012/2/5 Basil Chupin<blchupin@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.







--

kubuntu-users mailing list

kubuntu-users@lists.ubuntu.com

Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users


--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

basil and friends,

thanks for all your help, and yes its better to be safe than sorry, so
I won't concern
myself about it!

ray

On 2/5/12, Leslie Anne Chatterton <lahc2007@gmail.com> wrote:
> Basil,
>
> There is no "yes or no" answer possible.
>
> In a perfect world it wouldn't matter. Unfortunately minor errors in
> writing to disk will happen. Even though it's extremely rare, compared to
> the billions of bytes written, even one altered bit can trash a whole file
> or programme. Fortunately most errors can be corrected if caught quickly
> before they can start a cascade of consequent errors. That is what fsck is
> there to do.
>
> Now you could probably go for years without getting caught by this kind of
> disk corruption, but... wouldn't it be nice to have as much free and fast
> "insurance" as the wit of clever programmers can devise?
>
> I thought so. Now you have your answer.
>
> Sent from my Motorola Xoom Android tablet
> On Feb 5, 2012 5:30 AM, "Basil Chupin" <blchupin@iinet.net.au> wrote:
>
>> On 05/02/12 18:19, Jonas Norlander wrote:
>>
>>> 2012/2/5 Basil Chupin<blchupin@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.
>>
>>
>>
>> --
>> kubuntu-users mailing list
>> kubuntu-users@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/**
>> mailman/listinfo/kubuntu-users<https://lists.ubuntu.com/mailman/listinfo/kubuntu-users>
>>
>

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users

Hi,
Just my 2 cents worth. If you look at /etc/fstab at the entries for
each device, there are 2 numbers on the end of each entry, as I
understand things these are related to whether or not an "fsck" is done
on the associated device, again as I understand things, if these are set
to 0 then an "fsck" is not performed.
Also, if the machine is not shutdown cleanly, for example when
Ubuntu refuses to terminate and you are forced to physically power off
the shut the machine down (for whatever reason it can't shut down
normally), the disk is left flagged a "dirty" or is in an "unstable"
state. The next time you boot, the boot process takes a significant
amount of time to complete because the system is replaying all the
journaled transactions from the previous session (this is in the
situation where you are actually using a journaling file system). I have
been in the situation where requiring a physical power off to shut the
machine down has destroyed an ext3 file system.


regards,
Steve


On 06/02/12 06:44, ray burke wrote:

basil and friends,

thanks for all your help, and yes its better to be safe than sorry, so
I won't concern
myself about it!

ray

On 2/5/12, Leslie Anne Chatterton<lahc2007@gmail.com> wrote:

Basil,

There is no "yes or no" answer possible.

In a perfect world it wouldn't matter. Unfortunately minor errors in
writing to disk will happen. Even though it's extremely rare, compared to
the billions of bytes written, even one altered bit can trash a whole file
or programme. Fortunately most errors can be corrected if caught quickly
before they can start a cascade of consequent errors. That is what fsck is
there to do.

Now you could probably go for years without getting caught by this kind of
disk corruption, but... wouldn't it be nice to have as much free and fast
"insurance" as the wit of clever programmers can devise?

I thought so. Now you have your answer.

Sent from my Motorola Xoom Android tablet
On Feb 5, 2012 5:30 AM, "Basil Chupin"<blchupin@iinet.net.au> wrote:


On 05/02/12 18:19, Jonas Norlander wrote:


2012/2/5 Basil Chupin<blchupin@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.



--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/**
mailman/listinfo/kubuntu-users<https://lists.ubuntu.com/mailman/listinfo/kubuntu-users>

--
kubuntu-users mailing list
kubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users