From: Dave Chinner <david@fromorbit.com>
To: Shrinand Javadekar <shrinand@maginatics.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: Performance impact of mkfs.xfs vs mkfs.xfs -f
Date: Wed, 26 Aug 2015 09:43:00 +1000 [thread overview]
Message-ID: <20150825234300.GN714@dastard> (raw)
In-Reply-To: <CABppvi6W5_1GBrb8x1wOAq3X6yraTtt1UYEFE+dBzcXj3yTzrg@mail.gmail.com>
On Tue, Aug 25, 2015 at 04:09:33PM -0700, Shrinand Javadekar wrote:
> I did this on 2 different setups.
Details?
> Formatted the new disks with mkfs.xfs. Ran the workload.
> Reformatted the disks with mkfs.xfs -f. Ran the workload.
>
> >
> >> Any ideas why this might be happening?
> >
> > With the paucity of information you've provided, nope!
>
> Apologies. What more information can I provide?
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> > What version of xfsprogs are you using?
>
> # xfs_repair -V
> xfs_repair version 3.1.9
That's pretty old.
> > What was the output of mkfs.xfs each time; did the geometry differ?
>
> I have the output of xfs_info /mount/point from the first experiment
> and that of mkfs.xfs -f. One difference I see is that reformatting
> adds projid32bit=0 for the inode section.
xfs_info didn't get projid32bit status output until 3.2.0.
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.
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-25 23:43 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 [this message]
2015-08-26 0:39 ` Carlos E. R.
2015-08-26 1:09 ` Dave Chinner
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=20150825234300.GN714@dastard \
--to=david@fromorbit.com \
--cc=sandeen@sandeen.net \
--cc=shrinand@maginatics.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