From: Brian Foster <bfoster@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Bond Masuda <bond.masuda@jlbond.com>, linux-xfs@vger.kernel.org
Subject: Re: XFS issues with NVMe SSD
Date: Mon, 23 Jan 2017 08:50:48 -0500 [thread overview]
Message-ID: <20170123135048.GB33287@bfoster.bfoster> (raw)
In-Reply-To: <dbcc14e5-73e7-4ba0-22d2-646d3e466927@sandeen.net>
On Mon, Jan 23, 2017 at 07:41:58AM -0600, Eric Sandeen wrote:
> On 1/21/17 7:20 PM, Bond Masuda wrote:
> > Hi linux-xfs list:
> >
> > I've been having XFS file system corruption issues when used with
> > Intel NVMe SSD in Fedora 25 Linux as reported here:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1402533
> >
> > I don't know if this is XFS issue or not, but ext4 on the same Intel
> > NVMe SSD doesn't appear to be a problem. Are linux/xfs devs already
> > aware of the problem?
> >
> > Bond
>
> Well, the bug languished under anaconda, so no, we haven't seen it.
>
> It's pretty light on details. Please provide the install logs, dmesg output,
> xfs_repair output etc. I'll update the bug.
>
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?
>From the bug, it does seem like a reboot is a consistent factor to
reproduce the corruption. I wonder whether it's enough to have the
device mounted at reboot time, or if being a rootfs device is a primary
factor...
Brian
> -Eric
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-01-23 13:50 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 [this message]
2017-01-23 13:53 ` Christoph Hellwig
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=20170123135048.GB33287@bfoster.bfoster \
--to=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