From: Christoph Hellwig <hch@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
Bond Masuda <bond.masuda@jlbond.com>,
linux-xfs@vger.kernel.org
Subject: Re: XFS issues with NVMe SSD
Date: Mon, 23 Jan 2017 05:53:48 -0800 [thread overview]
Message-ID: <20170123135348.GA25320@infradead.org> (raw)
In-Reply-To: <20170123135048.GB33287@bfoster.bfoster>
On Mon, Jan 23, 2017 at 08:50:48AM -0500, Brian Foster wrote:
> Since this is limited hardware (I don't have access to such hardware, at
> least), it might also be helpful to see if you can isolate the problem
> from a full distro install. For example, can you format such a device
> external to the rootfs, mount, copy some stuff and reproduce the
> corruption after some sequence of unmount/remount/reboot operations?
I have plenty of NVMe hardware, although none of them is Intel and I've
never seen corruption like that. I also don't run Fedora, though :)
Does anyone know if the Fedora installer does a fstrim run or something
similar? I remember that most Intel NVMe devices had some pretty severe
deallocate (aka discard on NVMe) bugs. A firmware update might be a
good start in that case.
next prev parent reply other threads:[~2017-01-23 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 1:20 XFS issues with NVMe SSD Bond Masuda
2017-01-23 13:41 ` Eric Sandeen
2017-01-23 13:50 ` Brian Foster
2017-01-23 13:53 ` Christoph Hellwig [this message]
2017-01-23 21:25 ` Chris Murphy
2017-01-23 21:27 ` Eric Sandeen
2017-01-23 21:33 ` Chris Murphy
2017-01-24 2:13 ` Bond Masuda
2017-01-24 8:14 ` Gabriel VLASIU
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=20170123135348.GA25320@infradead.org \
--to=hch@infradead.org \
--cc=bfoster@redhat.com \
--cc=bond.masuda@jlbond.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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