From: Sunil Mushran <Sunil.Mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Add --force option in tunefs
Date: Wed, 02 Jul 2008 17:49:54 -0700 [thread overview]
Message-ID: <486C2232.606@oracle.com> (raw)
In-Reply-To: <20080702194431.GH29916@mail.oracle.com>
Well, we need to have a --force override if only to allow users
cloning ocfs2 volumes an easy way to change the uuid.
Goldwyn,
What is your justification for needing this feature? As in,
allowing force override to change mount type from clustered to local.
Is this a specific user requirement?
Our fear is that this override will allow some script author to
hard code it leading to corruption. As in, click here to change the
mount type. I mean, we already have a force override in mkfs, but
format is something users understand wipes the data. I am not sure
users will immediately understand that changing the mount type will
corrupt the fs if it is mounted on another node.
Sunil
Joel Becker wrote:
> On Wed, Jul 02, 2008 at 03:18:04PM +0530, Goldwyn Rodrigues wrote:
>
> Hey, there. Tools changes belong on
> ocfs2-tools-devel at oss.oracle.com, so I've copied that mailing list.
>
>
>> This patch enable --force option in tunefs.ocfs2
>> Like mkfs, the --force option ignores cluster initialization
>> and locking.
>>
>
> Thanks for the patch, but we decided long ago that we didn't
> want tunefs run without the cluster. That's why there is no force
> option. It's intentional.
>
> Joel
>
>
prev parent reply other threads:[~2008-07-03 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 9:48 [Ocfs2-devel] Add --force option in tunefs Goldwyn Rodrigues
2008-07-02 19:44 ` Joel Becker
2008-07-03 0:49 ` Sunil Mushran [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=486C2232.606@oracle.com \
--to=sunil.mushran@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.