public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Otto Wyss <otto.wyss@bluewin.ch>
Cc: Mark Hahn <hahn@physics.mcmaster.ca>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: How errorproof is ext2 fs?
Date: Fri, 14 Sep 2001 15:38:48 -0600	[thread overview]
Message-ID: <20010914153848.C1541@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10109140953100.24181-100000@coffee.psychology.mcmaster.ca> <3BA26CFA.E3859A7A@bluewin.ch>
In-Reply-To: <3BA26CFA.E3859A7A@bluewin.ch>

On Sep 14, 2001  22:47 +0200, Otto Wyss wrote:
> > there's no reason you can't configure your boot scripts to automatically
> > fix such problems.  and by "manually", I hope you meant that "fsck -y"
> > took 15 minutes to run.
> > ...
> What's this "-y" meaning, "man fsck" does not show it. Could this mean answer
> any question with "yes"? The 15 minutes I needed to answer about the first
> hundreds of questions with "y", afterwards I simply pressed "y" until the fsck
> was finished.

Well, the "best" way of running e2fsck is with the "-p" option, so that it
will pick y/n as appropriate.  In almost all cases "-p" and "-y" behave
the same, but in a few rare cases they do not.

In general, if you are manually fsck'ing a filesystem, it is better to
run fsck.<fstype> directly (and read its man page) instead of the "fsck"
wrapper program.

In some rare cases, fsck cannot decide what is the right thing to do, so
you need to run it in manual mode, which appears to be what happened to you.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert


  reply	other threads:[~2001-09-14 21:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10109140953100.24181-100000@coffee.psychology.mcmaster.ca>
2001-09-14 20:47 ` How errorproof is ext2 fs? Otto Wyss
2001-09-14 21:38   ` Andreas Dilger [this message]
2001-09-15  6:39 Timothy A. Seufert
  -- strict thread matches above, loose matches on Subject: below --
2001-09-14 13:09 Jesse Pollard
2001-09-13 21:30 Otto Wyss
2001-09-13 21:53 ` Joel Jaeggli
2001-09-13 22:05 ` Alan Cox
2001-09-14 19:16   ` Otto Wyss
2001-09-14 20:39     ` Mike Fedyk
2001-09-16  8:58   ` Rogier Wolff
2001-09-16 10:00     ` Frank Schneider
2001-09-16 10:14     ` Luigi Genoni
     [not found] ` <3BA1E670.9010300@foogod.com>
2001-09-14 20:37   ` Otto Wyss
2001-09-14 23:09     ` Alan Cox

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=20010914153848.C1541@turbolinux.com \
    --to=adilger@turbolabs.com \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=otto.wyss@bluewin.ch \
    /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