From: Christoph Hellwig <hch@infradead.org>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Weird behaviour of mkfs.xfs
Date: Sat, 26 Mar 2016 09:36:42 -0700 [thread overview]
Message-ID: <20160326163642.GA19464@infradead.org> (raw)
In-Reply-To: <20160326154619.3649ebdf@harpe.intellique.com>
On Sat, Mar 26, 2016 at 03:46:19PM +0100, Emmanuel Florac wrote:
> Actually I was too impatient; it finally ended avec 30 minutes of
> burning bits to the flash. I don't understand the behaviour, though.
> I'm used to mkfs.xfs making its magic extremely quickly, even on
> humongous devices. Here it's a very fast array of only 3.2 TB...
Trey doing a mkfs.xfs -K, without that it diascards the whole device.
I've seen some NVMe device misbehaving under discard storms, up to
the point of resetting the controller..
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-03-26 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 13:50 Weird behaviour of mkfs.xfs Emmanuel Florac
2016-03-26 14:46 ` Emmanuel Florac
2016-03-26 16:36 ` Christoph Hellwig [this message]
2016-03-28 15:18 ` Emmanuel Florac
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=20160326163642.GA19464@infradead.org \
--to=hch@infradead.org \
--cc=eflorac@intellique.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