From: Eric Sandeen <sandeen@sandeen.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: Small change for mkfs.xfs?
Date: Sun, 28 Feb 2010 16:37:32 -0600 [thread overview]
Message-ID: <4B8AF02C.3070904@sandeen.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1002270628120.17433@p34.internal.lan>
Justin Piszcz wrote:
> Hi,
>
> # mkfs.xfs /dev/md0
> mkfs.xfs: /dev/md0 appears to contain an existing filesystem (ext3).
> mkfs.xfs: Use the -f option to force overwrite.
>
> This occurs if the filesystem is ext4. Need to differentiate between
> the two FS if possible?
Why, you're just overwriting it anyway ;)
FWIW, recent xfsprogs built against recent libblkid will detect ext4 correctly.
libdisk could be patched if anyone really cared enough but that's deprecated
going forward...
-Eric
> Justin.
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-02-28 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 11:29 Small change for mkfs.xfs? Justin Piszcz
2010-02-28 22:37 ` Eric Sandeen [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=4B8AF02C.3070904@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jpiszcz@lucidpixels.com \
--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