public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: <speakup@braille.uwo.ca>
Subject: Re: how to fix the file system?
Date: Mon, 29 Sep 2003 14:04:59 -0600	[thread overview]
Message-ID: <000c01c386c4$f83f5d00$6400a8c0@merlin> (raw)
In-Reply-To: <20030929121737.GA163@lnx3.holmesgrown.com>

Well, journaling is not fool proof, but it will usually allow you to recover
with very little difficulty. When fsck runs, it first checks to see if the
filesystem has a journal. If so, it replays it to recover the filesystem.
Then, it checks to seeif a bit has been set in the filesystem which
indicates other errors. If the bit is set, it performs a complete check to
repair any damages.
--
Joseph C. Lininger
jbahm@pcdesk.net
----- Original Message ----- 
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Monday, September 29, 2003 6:17 AM
Subject: Re: how to fix the file system?


> Yes, ext3 makes things much better.  However, I had a recent power
> failure which caused my system to come back up but I ended up with
> some errors during reboot.  I had to fight my way through.  Most times
> though, the journal feature of ext3 saved my butt.  I still wonder if
> the errors I got weren't specific hard drive problems I might be
> having - have to see on that one.
>
> On Mon, Sep 29, 2003 at 12:47:12AM -0600, Joseph C. Lininger wrote:
> > System will most likely run fsck automatically. Actually, if your
running
> > Redhat 9, you've probably got ext3 filesystem which does not need to be
> > checked after this happens. It will simply recover the journal.
> > --
> > Joseph C. Lininger
> > jbahm@pcdesk.net
>
> -- 
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>



      reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jared
 ` Hugh Esco
 ` Guy Abandon.
 ` Charles Crawford
   ` Guy Abandon.
 ` Joseph C. Lininger
   ` Steve Holmes
     ` Joseph C. Lininger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000c01c386c4$f83f5d00$6400a8c0@merlin' \
    --to=jbahm@pcdesk.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).