linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Eric Sandeen <sandeen@redhat.com>, Theodore Tso <tytso@mit.edu>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: e2fsck -y says "yes" to "Abort?"
Date: Mon, 20 Apr 2009 14:47:04 -0600	[thread overview]
Message-ID: <20090420204704.GG3209@webber.adilger.int> (raw)
In-Reply-To: <49ECC12B.5090602@redhat.com>

On Apr 20, 2009  14:38 -0400, Ric Wheeler wrote:
> Eric Sandeen wrote:
>> Ric Wheeler wrote:
>>> The only down side is when you try to automate this (say in an  
>>> appliance) and you don't have a human reading the output. In this 
>>> case, you might just want to invert the logic but in general, it does 
>>> seem dangerous to invert the logic for a long standing option,
>>
>> Maybe make something like "-yy" automatically answer "n" to anything
>> that would stop the fsck, and answer "y" to anything that it proposes
>> fixing?
>   
> That would be useful for scripting users - it is already assumed to be  
> wildly dangerous to run it in "yes" mode I would assume in any case :-)

Well, all of the questions are designed to choose a safe option when
run with "-y", and to avoid changing the filesystem when run with "-n".

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.


      reply	other threads:[~2009-04-20 20:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-18 14:10 e2fsck -y says "yes" to "Abort?" Eric Sandeen
2009-04-18 16:17 ` Theodore Tso
2009-04-20 18:29   ` Ric Wheeler
2009-04-20 18:33     ` Eric Sandeen
2009-04-20 18:38       ` Ric Wheeler
2009-04-20 20:47         ` Andreas Dilger [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=20090420204704.GG3209@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=rwheeler@redhat.com \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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 NNTP newsgroup(s).