All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Neal Gieselman <Neal.Gieselman@Visionics.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 fsck question
Date: Thu, 1 Mar 2001 13:04:13 +0000	[thread overview]
Message-ID: <20010301130413.B7647@redhat.com> (raw)
In-Reply-To: <D0FA767FA2D5D31194990090279877DA57328F@dbimail.digitalbiometrics.com>
In-Reply-To: <D0FA767FA2D5D31194990090279877DA57328F@dbimail.digitalbiometrics.com>; from Neal.Gieselman@Visionics.com on Wed, Feb 28, 2001 at 08:03:21PM -0600

Hi,

On Wed, Feb 28, 2001 at 08:03:21PM -0600, Neal Gieselman wrote:
> 
> I applied the libs and other utilites from e2fsprogs by hand.
> I ran fsck.ext3 on my secondary partition and it ran fine.  The boot fsck
> on / was complaining about something but I could not catch it.
> I then went single user and ran fsck.ext3 on / while mounted.

e2fsck should complain loudly and ask for confirmation if you do that.
Goin ahead with the fsck is a bad move on a mounted, rw filesystem!

> Excuse the stupid question, but with ext3, do I really require the
> fsck.ext3?  

fsck.ext3 is just a link to e2fsck.  Make sure you're running recent
e2fsprogs, though (either the latest snapshot from
downloads.sourceforge.net or a build from
ftp.uk.linux.org:/pub/linux/sct/fs/jfs/).

Cheers,
 Stephen

      parent reply	other threads:[~2001-03-01 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01  2:03 ext3 fsck question Neal Gieselman
2001-03-01 12:59 ` Richard B. Johnson
2001-03-01 13:04 ` Stephen C. Tweedie [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=20010301130413.B7647@redhat.com \
    --to=sct@redhat.com \
    --cc=Neal.Gieselman@Visionics.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.