From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-ext4@vger.kernel.org
Subject: Re: [PATCH][RESEND] mke2fs: fix force option to create filesystem on mounted device
Date: Fri, 25 Oct 2013 13:30:31 -0200 [thread overview]
Message-ID: <20131025152957.GA14944@orion.maiolino.org> (raw)
In-Reply-To: <526A2E83.5050102@sx.jp.nec.com>
Looks good,
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
On Fri, Oct 25, 2013 at 05:40:35PM +0900, Kazuya Mio wrote:
> According to mke2fs man, we can create a filesystem on the mounted device
> when -FF option is specified.
> However, currently we have to specify -F option third to force mke2fs.
> This patch fixes the problem.
>
> Signed-off-by: Kazuya Mio <k-mio@sx.jp.nec.com>
> Reviewed-by: Zheng Liu <wenqing.lz@taobao.com>
> ---
> misc/util.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/misc/util.c b/misc/util.c
> index 6c93e1c..40c8858 100644
> --- a/misc/util.c
> +++ b/misc/util.c
> @@ -150,7 +150,7 @@ void check_mount(const char *device, int force, const char *type)
> }
> if (mount_flags & EXT2_MF_MOUNTED) {
> fprintf(stderr, _("%s is mounted; "), device);
> - if (force > 2) {
> + if (force >= 2) {
> fputs(_("mke2fs forced anyway. Hope /etc/mtab is "
> "incorrect.\n"), stderr);
> return;
> @@ -162,7 +162,7 @@ void check_mount(const char *device, int force, const char *type)
> if (mount_flags & EXT2_MF_BUSY) {
> fprintf(stderr, _("%s is apparently in use by the system; "),
> device);
> - if (force > 2) {
> + if (force >= 2) {
> fputs(_("mke2fs forced anyway.\n"), stderr);
> return;
> }
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Carlos
prev parent reply other threads:[~2013-10-25 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 8:40 [PATCH][RESEND] mke2fs: fix force option to create filesystem on mounted device Kazuya Mio
2013-10-25 15:30 ` Carlos Maiolino [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=20131025152957.GA14944@orion.maiolino.org \
--to=cmaiolino@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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