From: Emmanuel Florac <eflorac@intellique.com>
To: linux-xfs@vger.kernel.org
Cc: Andrea Mazzocchi <mazzocchiandrea24@gmail.com>
Subject: Re: XFS corruption of in-memory data detected with KVM
Date: Thu, 22 Feb 2018 12:33:51 +0100 [thread overview]
Message-ID: <20180222123351.256227f2@harpe.intellique.com> (raw)
In-Reply-To: <CAJbUkCQd_TOOSxVwWzDca7Do6_g+dMsKU3fObMig4gG_0HHg-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
Le Thu, 22 Feb 2018 10:11:08 +0100
Andrea Mazzocchi <mazzocchiandrea24@gmail.com> écrivait:
Please keep the list cc'ed, in case someone comes with another idea.
> > Hard to say, what KVM disk format are you using? Raw, qcow2, LVM
> > volumes? If these are files (raw or qcow2), what kind of filesystem
> > and hardware stack are they living on? Are there any error on the
> > hosting system?
>
> Software configuration of provider's hypervisor host nodes is held in
> confidentiality:
> I can't know KVM version and configurations, unless something is
> shown in dmesg.
Hum, so we can't know for sure if something went wrong outside the VM,
annoying.
> > At tne VM level, do you see any IO error? Are you using the virtio
> > disk driver or something else?
>
> The errors we saw were: we failed to establish an SSH connection,
> so we went to the provider's console of the VPS and the dmesg was
> shown: the log seemed all fine until "systemd[1]: found device
> /dev/mapper/centos-root"
> (which is where it begins the dmesg I posted).
> We are using virtio disk driver.
I see. Now you'll need to boot the VM from some rescue system (possibly
the installation image of CentOS) to run xfs_repair before going any
further, unfortunately.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-02-22 11:34 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
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 [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=20180222123351.256227f2@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mazzocchiandrea24@gmail.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;
as well as URLs for NNTP newsgroup(s).