fsck on mounted system?
Basil Chupin
blchupin at iinet.net.au
Fri Sep 7 13:12:46 UTC 2012
On 07/09/12 20:16, Nils Kassube wrote:
> oxy wrote:
>> it is nowadays common to have a big partition in your system with
>> almost everything. When you have some energy blackouts and
>> want to check for the integrity of your discs, how do you do it?
> Use the command
>
> sudo touch /forcefsck
>
> and then the filesystem should be checked at the next reboot.
>
>
>
> Nils
The file system is checked at boot time anyway.
However, if there are serious problems they are not corrected and you
need to run e2fsck manually. Here I speak from experience.
We had a couple of power failures during severe storms following which
my wife's computer played up for several days (computer was booted every
morning). On a hunch I did e2fsck manually and found bad corruption of
the file system which I then had e2fsck repair. Problem disappeared.
In another place, I gave another person same advice and he came back
stating that his fs was also corrupted and e2fsck repaired the damage.
When running e2fsck manually do NOT use the '-p' option; watch what
e2fsck shows you as problem(s) and answer the questions (all usually in
the affirmative).
(And it doesn't hurt to run e2fsck occasionally either - it won't do any
harm but it may just reveal some problem in the file system which
developed for some reason.
BTW, if you are using reiser file system then run 'reiserfsck
--fix-fixable'.)
BC
--
Using openSUSE 12.2 x86_64 KDE 4.9.1 & kernel 3.5.3-1 on a system with-
AMD FX 8-core 3.6/4.2GHz processor
16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM
Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU
More information about the ubuntu-users
mailing list