From: Martin Steigerwald <Martin@lichtvoll.de>
To: Ankur Tank <Ankur.Tank@lnttechservices.com>
Cc: Anand Jain <Anand.Jain@oracle.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs doesn't format eMMC if previous filesystem is ext4
Date: Mon, 29 Dec 2014 11:18:28 +0100 [thread overview]
Message-ID: <1638201.NiAcHcsd0T@merkaba> (raw)
In-Reply-To: <CFB3B8F56DDE9F45B45EBDEBED372A66442494@POCITMSEXMB05.LntUniverse.com>
Am Montag, 29. Dezember 2014, 09:55:13 schrieb Ankur Tank:
> Thank you for reply Anand & Matrin,
>
> Okay I understand the intention now.
> I know it's not the forum to address issues related to mkfs commands
> But I think, options used should be same across the mkfs.XXX commands.
> Another irregularity is
> mkfs.f2fs takes "-l" to apply label, while
> mkfs.ext4 take "-L" to apply label.
> If one has to write a common script these cases has to be handled separately.
>
> Anyways thank you for help,
Well, it is *one* of the forums. For that you probably need to CC every
filesystem development mailing list :) or as an alternative the common
fsdevel mailing list.
And yes, mkfs.reiserfs also takes -l. And the mkfs wrapper does *not* convert
the option. So if you use mkfs -t reiserfs -L it doesn´t work. That is why I
always use the mkfs.<FS> manpage and tool directly.
I think all mkfs tools should do the blkid check and not overwrite an
existing filesystem just so.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2014-12-29 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 15:24 btrfs doesn't format eMMC if previous filesystem is ext4 Ankur Tank
2014-12-26 20:05 ` Zygo Blaxell
2014-12-29 2:50 ` Anand Jain
2014-12-29 7:15 ` Ankur Tank
2014-12-29 9:38 ` Martin Steigerwald
2014-12-29 9:55 ` Ankur Tank
2014-12-29 10:18 ` Martin Steigerwald [this message]
2014-12-30 6:53 ` Ankur Tank
2014-12-29 9:55 ` Anand Jain
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=1638201.NiAcHcsd0T@merkaba \
--to=martin@lichtvoll.de \
--cc=Anand.Jain@oracle.com \
--cc=Ankur.Tank@lnttechservices.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).