From: Andrea Mazzocchi <mazzocchiandrea24@gmail.com>
To: Andrea Mazzocchi <mazzocchiandrea24@gmail.com>,
linux-xfs@vger.kernel.org
Subject: Re: XFS corruption of in-memory data detected with KVM
Date: Wed, 21 Feb 2018 16:23:43 +0100 [thread overview]
Message-ID: <CAJbUkCRN3p-o7qKjad+zOFEJ9cRMoop1TjFhG7pt6ConjdEL5w@mail.gmail.com> (raw)
In-Reply-To: <20180221114627.tbdequwrbmsakvcu@odin.usersys.redhat.com>
> Also, you are running a very old kernel, so, please make sure you try to run a
> newer xfs_repair.
We installed yesterday 3.10.0-693.17.1.el7. I know that CentOS and RedHat
keep old stable kernel version and backport important stuff: do you think that
upgrading to a more recent kernel (4 and above) would be better,
even if less stable?
> Also, this is more a guess than anything. If you see this happening often (even
> after xfs_repair), you might want to double-check your storage stack and see if
> this is not corrupting anything, bad configured storage stacks in virtual
> environments are very usual culprits on filesystem corruption cases.
How could we check our storage stack and see if it is the one to blame?
Thanks, best regards
next prev parent reply other threads:[~2018-02-21 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 10:57 XFS corruption of in-memory data detected with KVM Andrea Mazzocchi
2018-02-21 11:46 ` Carlos Maiolino
2018-02-21 15:23 ` Andrea Mazzocchi [this message]
2018-02-21 16:55 ` Emmanuel Florac
2018-02-22 10:22 ` Carlos Maiolino
2018-02-22 11:31 ` Andrea Mazzocchi
2018-02-22 13:50 ` Emmanuel Florac
[not found] ` <CAJbUkCQd_TOOSxVwWzDca7Do6_g+dMsKU3fObMig4gG_0HHg-w@mail.gmail.com>
2018-02-22 11:33 ` 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=CAJbUkCRN3p-o7qKjad+zOFEJ9cRMoop1TjFhG7pt6ConjdEL5w@mail.gmail.com \
--to=mazzocchiandrea24@gmail.com \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).