From: Marat Khalili <mkh@rqc.ru>
To: Linux fs Btrfs <linux-btrfs@vger.kernel.org>
Subject: qemu-kvm VM died during partial raid1 problems of btrfs
Date: Tue, 12 Sep 2017 11:02:13 +0300 [thread overview]
Message-ID: <2ee9f15b-a11a-886e-2460-557bb9f8d41d@rqc.ru> (raw)
Thanks to the help from the list I've successfully replaced part of
btrfs raid1 filesystem. However, while I waited for best opinions on the
course of actions, the root filesystem of one the qemu-kvm VMs went
read-only, and this root was of course based in a qcow2 file on the
problematic btrfs (the root filesystem of the VM itself is ext4, not
btrfs). It is very well possible that it is a coincidence or something
inducted by heavier than usual IO load, but it is hard for me to ignore
the possibility that somehow the hardware error was propagated to VM. Is
it possible?
No other processes on the machine developed any problems, but:
(1) it is very well possible that problematic sector belonged to this
qcow2 file;
(2) it is a Kernel VM after all, and it might bypass normal IO paths of
userspace processes;
(3) it is possible that it uses O_DIRECT or something, and btrfs raid1
does not fully protect this kind of access.
Does this make any sense?
I could not login to the VM normally to see logs, and made big mistake
of rebooting it. Now all I see in its logs is big hole, since, well, it
went read-only :( I'll try to find out if (1) above is true after I
finish migrating data from HDD and remove the it. I wonder where else
can I look?
--
With Best Regards,
Marat Khalili
next reply other threads:[~2017-09-12 8:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 8:02 Marat Khalili [this message]
2017-09-12 8:25 ` qemu-kvm VM died during partial raid1 problems of btrfs Timofey Titovets
2017-09-12 8:42 ` Marat Khalili
2017-09-12 9:21 ` Timofey Titovets
2017-09-12 9:29 ` Marat Khalili
2017-09-12 9:35 ` Timofey Titovets
2017-09-12 10:01 ` Duncan
2017-09-12 10:32 ` Adam Borowski
2017-09-12 10:39 ` Marat Khalili
2017-09-12 11:01 ` Timofey Titovets
2017-09-12 11:12 ` Adam Borowski
2017-09-12 11:17 ` Timofey Titovets
2017-09-12 11:26 ` Marat Khalili
2017-09-12 17:21 ` Adam Borowski
2017-09-12 17:36 ` Austin S. Hemmelgarn
2017-09-12 18:43 ` Adam Borowski
2017-09-12 18:47 ` Christoph Hellwig
2017-09-12 19:12 ` Austin S. Hemmelgarn
2017-09-12 19:11 ` Austin S. Hemmelgarn
2017-09-12 20:00 ` Adam Borowski
2017-09-12 20:12 ` Austin S. Hemmelgarn
2017-09-12 21:13 ` Adam Borowski
2017-09-13 0:52 ` Timofey Titovets
2017-09-13 12:55 ` Austin S. Hemmelgarn
2017-09-13 12:21 ` Austin S. Hemmelgarn
2017-09-18 11:53 ` Adam Borowski
2017-09-13 14:47 ` Martin Raiber
2017-09-13 15:25 ` Austin S. Hemmelgarn
2017-09-12 11:09 ` Roman Mamedov
2017-09-13 13:23 ` Chris Murphy
2017-09-13 14:15 ` Marat Khalili
2017-09-13 17:52 ` Goffredo Baroncelli
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=2ee9f15b-a11a-886e-2460-557bb9f8d41d@rqc.ru \
--to=mkh@rqc.ru \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.