public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH RFC] xfsprogs: suggest "-d" option for repair of RO mount
Date: Mon, 18 Nov 2013 06:56:14 +1100	[thread overview]
Message-ID: <20131117195614.GU6188@dastard> (raw)
In-Reply-To: <52851CA9.8080903@sandeen.net>

On Thu, Nov 14, 2013 at 12:55:37PM -0600, Eric Sandeen wrote:
> On 11/13/13, 6:59 AM, Carlos Maiolino wrote:
> > Hm, even in single user with a RO root filesystem, changing filesystem
> > on-disk filesystem structures without have them replied in memory looks
> > dangerous to me, you will keep data consistency since the fs is RO, but how
> > about memory? You might have a discrepancy between memory and disk metadata
> > contents causing in-memory only problems?
> > 
> 
> The possibility is already there; it's just a question of whether we
> suggest using it.  And my other patch suggests an immediate reboot
> when it's done, for just those reasons.

If you make the suggestion of using -d, then it should mention at
that point in time it's dangerous.

> A user needs some way to repair their root disk if they can't boot
> a rescue environment... and ext2/3/4 have been doing this since forever.
> 
> I know, none of the above are exactly arguments that its' safe... :)

Right, so let's make sure we don't give people any impression it is
safe :)

> >> +_("Unmount or use -d to repair a read-only mounted filesystem\n"));

_("Unmount or use the dangerous (-d) option to repair a read-only mounted filesystem\n"));

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-11-17 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 17:13 [PATCH RFC] xfsprogs: suggest "-d" option for repair of RO mount Eric Sandeen
2013-11-13 12:59 ` Carlos Maiolino
2013-11-14 18:55   ` Eric Sandeen
2013-11-17 19:56     ` Dave Chinner [this message]
2013-11-18 15:56       ` Eric Sandeen
2013-11-18 16:02 ` [PATCH V2] " Eric Sandeen
2013-11-18 22:26   ` Dave Chinner
2013-12-03 14:42   ` Rich Johnston

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=20131117195614.GU6188@dastard \
    --to=david@fromorbit.com \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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