From: Eric Sandeen <sandeen@sandeen.net>
To: Shrinand Javadekar <shrinand@maginatics.com>,
Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Performance impact of mkfs.xfs vs mkfs.xfs -f
Date: Wed, 26 Aug 2015 14:04:51 -0500 [thread overview]
Message-ID: <55DE0DD3.90108@sandeen.net> (raw)
In-Reply-To: <CABppvi7AYbqiskyrEp3As6RPyRz0pThoqVEcjX4736KV-wLkCA@mail.gmail.com>
On 8/26/15 12:48 PM, Shrinand Javadekar wrote:
>>>>> >> >> 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
> [Shri] I mentioned this in my first email. Here's the information:
> http://oss.sgi.com/archives/xfs/2015-06/msg00108.html
Just as an aside:
A 3 month old email under a different subject doesn't really help
us in this thread. ;)
You're the only one who knows if this is the same machine, whether you've
upgraded since, etc. So we had to ask...
For anyone reading:
If you're having a problem, please, please always start with as much information
about your environment as you can provide, as described in the xfs.org URL
above. It saves many email round-trips, and helps us help you better.
Thanks,
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-08-26 19:04 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
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 [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=55DE0DD3.90108@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--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 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.