On Monday 26 April 2004 14:17, Farrell, Kevin wrote:
> Journalised filesystems work by saving filesystem "meta data" at periodic
> intervals (checkpoints). If a system crashes, by power failure or by the
> kernel crashing for example, and if the hardware isn't damaged, then the
> filesystem can be automatically rebuilt relatively quickly from the most
> recent checkpoint with a complete "journal".
But why then did the system not boot properly,
but come up in "single user" mode, with a request to fsck?
I can say from my experience with a bad disk
(on what is now my second-nest laptop),
which currently lasts an average of 5 minutes after booting,
that about 1 time in 5 it comes up in single user mode.
However, in my case I found that if one simply ignores
the request to fsck, and just re-boots,
it usually comes up OK the second time.
So I am slightly puzzled why I get the request to fsck,
and why if can't use the latest journalling record, as you suggest.
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
