cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [Linux-cluster] Feature Request: gfs_fsck has a yes to all response.
Date: Thu, 26 Feb 2009 11:04:27 -0500 (EST)	[thread overview]
Message-ID: <1644791071.85631235664267778.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <47246377.85441235664186405.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>

----- "Stewart Walters" <spods@iinet.net.au> wrote:
| Thanks Bob, but I was sort of hoping for an option of doing "yes to
| all" once
| you've already started the fsck. I'm not exactly sure if there is any
| fallout to
| stopping gfs_fsck part way through it's repair operations on a broken
| GFS volume.
| 
| Not to worry - Does anyone know what's going on with that weird 'Fix
| bitmap for
| block' number continually changing when you press the Enter key?
| 
| I suppose this is a weird gfs_fsck display quirk when the response is
| not a 'y'
| or a 'n'.
| 
| Regards,
| 
| Stewart

Hi Stewart,

An "a" (all) answer to the yes/no questions is certainly easy to do.
I've thought about doing it, too, but AFAIK, none of the other fscks
allow this response.  I'll ask around and see if anyone objects.

Regards,

Bob Peterson
Red Hat GFS



       reply	other threads:[~2009-02-26 16:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47246377.85441235664186405.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2009-02-26 16:04 ` Bob Peterson [this message]
     [not found] <31034.1235450248@iinet.net.au>
2009-02-24  5:04 ` [Cluster-devel] Re: [Linux-cluster] Feature Request: gfs_fsck has a yes to all response Bob Peterson

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=1644791071.85631235664267778.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com \
    --to=rpeterso@redhat.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 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).