From: Dave Chinner <david@fromorbit.com>
To: "Carlos E. R." <carlos.e.r@opensuse.org>
Cc: XFS mailing list <xfs@oss.sgi.com>
Subject: Re: Performance impact of mkfs.xfs vs mkfs.xfs -f
Date: Wed, 26 Aug 2015 11:09:23 +1000 [thread overview]
Message-ID: <20150826010923.GX3902@dastard> (raw)
In-Reply-To: <55DD0AAF.9090401@opensuse.org>
On Wed, Aug 26, 2015 at 02:39:11AM +0200, Carlos E. R. wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 2015-08-26 01:43, Dave Chinner wrote:
> > On Tue, Aug 25, 2015 at 04:09:33PM -0700, Shrinand Javadekar
> > wrote:
>
> >> Formatted the new disks with mkfs.xfs. Ran the workload.
> >> Reformatted the disks with mkfs.xfs -f. Ran the workload.
>
>
> > Anyway, please post the output so we can see the differences for
> > ourselves. What we need is mkfs output in both cases, and xfs_info
> > output in both cases after mount.
>
> Suggestion (for the OP):
>
> To reformat a third time without "-f", you can reformat as ext4, then
> format a second time as xfs.
That doesn't work - mkfs.xfs detects that the device has an ext4
filesystem on it, and demands you use -f to overwrite it.
> But to imitate a new disk, you have to
> zero it with dd.
Only the first MB or so - enough for blkid not to be able to see a
filesystem signature on it.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-08-26 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 20:32 Performance impact of mkfs.xfs vs mkfs.xfs -f Shrinand Javadekar
2015-08-25 21:24 ` Shrinand Javadekar
2015-08-25 21:44 ` Eric Sandeen
2015-08-25 23:09 ` Shrinand Javadekar
2015-08-25 23:43 ` Dave Chinner
2015-08-26 0:39 ` Carlos E. R.
2015-08-26 1:09 ` Dave Chinner [this message]
2015-08-26 7:25 ` Martin Steigerwald
2015-08-26 17:48 ` Shrinand Javadekar
2015-08-26 18:44 ` Eric Sandeen
2015-08-26 19:04 ` Eric Sandeen
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=20150826010923.GX3902@dastard \
--to=david@fromorbit.com \
--cc=carlos.e.r@opensuse.org \
--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 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.