From: Oleg Drokin <green@namesys.com>
To: Steve Pratt <slpratt@us.ibm.com>
Cc: reiserfs-list@namesys.com
Subject: Re: A couple of questions
Date: Thu, 16 May 2002 22:55:30 +0400 [thread overview]
Message-ID: <20020516225530.A4142@namesys.com> (raw)
In-Reply-To: <OF4AF5C20B.BE2F7D18-ON85256BBB.006643F3@pok.ibm.com>
Hello!
On Thu, May 16, 2002 at 01:44:16PM -0500, Steve Pratt wrote:
> One extra question on this. I assume that if in Fix mode and errors are
> encountered that fsck.resiserfs will prompt to fix each error and that
> there is no way to have it answer 'Yes' automatically like the ext2 -y
> option.
I am unaware of a situation where reiserfsck asks any question in the middle of
repairing.
It may ask for more than one confirmation in the beginning (one of the cases
being when it thinks it may replay a journal, but it is not sure).
But these cases are really the cases where you want to pass the question
to user and get his opinition to pass it to fsck.
I think they all are looks very similar, so you can find them quickly in output
stream (something like some text and then "(y/n):" sequence of characters).
When fs bugs are fixed, this is done without any questions asked,
and though this is somewhat questionable approach, this is how it done at
present.
> If not then I will probably have to take Jonathan Briggs suggestion of a
> third process to answer 'Yes' repeatedly.
This is very dangerous approach. There is exactly one "extra" confirmation,
the one at the beginning, where reiserfsck asks if you really want to run it.
All of the others are really important. (well, may be not all, but most of them
for sure)
Bye,
Oleg
next prev parent reply other threads:[~2002-05-16 18:55 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-16 18:44 A couple of questions Steve Pratt
2002-05-16 18:55 ` Oleg Drokin [this message]
2002-05-16 20:33 ` Hans Reiser
2002-05-16 21:23 ` Kuba Ober
2002-05-16 21:44 ` Lehmann
2002-05-16 23:57 ` Hans Reiser
2002-05-17 0:45 ` Philipp Gühring
2002-05-17 1:06 ` Manuel Krause
2002-05-17 15:21 ` Kuba Ober
2002-05-17 0:17 ` Manuel Krause
2002-05-17 15:04 ` Kuba Ober
2002-05-18 20:40 ` Hans Reiser
2002-05-17 15:05 ` Kuba Ober
2002-05-16 21:44 ` Lehmann
2002-05-17 13:10 ` Valdis.Kletnieks
2002-05-17 15:35 ` Kuba Ober
-- strict thread matches above, loose matches on Subject: below --
2010-05-27 13:39 Paul Millar
2010-05-27 14:56 ` Hubert Kario
2010-05-31 17:59 ` Paul Millar
2010-06-02 16:19 ` Hubert Kario
2010-05-27 16:00 ` Chris Mason
2010-05-31 18:06 ` Paul Millar
2010-05-31 20:33 ` Mike Fedyk
2010-06-02 11:56 ` Paul Millar
2010-06-01 13:39 ` Martin K. Petersen
2010-06-02 13:40 ` Paul Millar
2010-06-04 1:17 ` Martin K. Petersen
2005-04-18 11:51 Imre Simon
2005-04-18 15:31 ` Linus Torvalds
2005-04-18 16:23 ` Paul Jackson
2002-05-17 15:27 Steve Pratt
2002-05-17 13:11 berthiaume_wayne
2002-05-17 16:03 ` Kuba Ober
2002-05-16 18:48 Steve Pratt
2002-05-16 15:11 Steve Pratt
2002-05-16 15:35 ` Oleg Drokin
2002-05-16 14:52 Steve Pratt
2002-05-16 15:13 ` Hans Reiser
2002-05-15 21:22 Steve Pratt
2002-05-16 5:20 ` Oleg Drokin
2002-05-16 9:42 ` Hans Reiser
2002-05-16 11:40 ` Oleg Drokin
2002-05-16 11:54 ` Hans Reiser
2001-10-10 11:28 Adil EL YOUSSEFI
2001-10-10 12:11 ` David Woodhouse
1999-03-02 13:11 Neil Booth
1999-03-15 18:58 ` Stephen C. Tweedie
1999-03-15 22:46 ` neil
1999-03-16 12:22 ` Stephen C. Tweedie
1999-03-16 2:11 ` Andrea Arcangeli
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=20020516225530.A4142@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=slpratt@us.ibm.com \
/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.