From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: "MASON, CHRISTOPHER" <CHRIS.MASON@oracle.com>,
xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfsprogs: add btrfs detection to libdisk
Date: Thu, 8 Jan 2009 14:12:37 -0500 [thread overview]
Message-ID: <20090108191237.GD10617@infradead.org> (raw)
In-Reply-To: <49664243.1090405@redhat.com>
On Thu, Jan 08, 2009 at 12:13:23PM -0600, Eric Sandeen wrote:
> Now that the btrfs disk format has stabilized, libdisk can
> recognize it and mkfs.xfs will not overwrite it w/o "-f" :
>
> # mkfs.btrfs -l 16384 -L mylabel -n 8192 -s 4096 /tmp/fsfile
> fs created label mylabel on /tmp/fsfile
> nodesize 8192 leafsize 16384 sectorsize 4096 size 1.28GB
> Btrfs v0.16-37-gb8271dc
> # mkfs.xfs /tmp/fsfile
> mkfs.xfs: /tmp/fsfile appears to contain an existing filesystem (btrfs).
> mkfs.xfs: Use the -f option to force overwrite.
Looks good.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-01-08 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 18:13 [PATCH] xfsprogs: add btrfs detection to libdisk Eric Sandeen
2009-01-08 19:12 ` Christoph Hellwig [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=20090108191237.GD10617@infradead.org \
--to=hch@infradead.org \
--cc=CHRIS.MASON@oracle.com \
--cc=sandeen@redhat.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