BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] systemd reboot
- Subject: [Discuss] systemd reboot
- From: richard.pieri at gmail.com (Richard Pieri)
- Date: Mon, 5 Mar 2018 19:27:08 -0500
- In-reply-to: <chxr2oycs1t.fsf@sdf.org>
- References: <chx371hap0u.fsf@sdf.org> <20180303041119.3148add8@mydesk.domain.cxm> <chxd10kft5v.fsf@sdf.org> <73b0b5ed-def9-e3e4-b678-d5fba4dfcfe3@gmail.com> <chxr2oycs1t.fsf@sdf.org>
On 3/5/2018 1:10 PM, Mike Small wrote: > Thanks, this is great info. Curiously, in my local reproduction of the > issue the lying hardware involved is qemu's virtio simulated disk. So > maybe their simulation is super realistic, eh? No. Virtio is a bridge between guests and host. It doesn't simulate anything. I still don't think that this is the real root cause, though. Only because the time I did see something like what you describe the cause was an inconsistent mirror set. -- Rich P.
- Follow-Ups:
- [Discuss] systemd reboot
- From: smallm at sdf.org (Mike Small)
- [Discuss] systemd reboot
- References:
- [Discuss] systemd reboot
- From: smallm at sdf.org (Mike Small)
- [Discuss] systemd reboot
- From: slitt at troubleshooters.com (Steve Litt)
- [Discuss] systemd reboot
- From: smallm at sdf.org (Mike Small)
- [Discuss] systemd reboot
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] systemd reboot
- From: smallm at sdf.org (Mike Small)
- [Discuss] systemd reboot
- Prev by Date: [Discuss] systemd reboot
- Next by Date: [Discuss] systemd reboot
- Previous by thread: [Discuss] systemd reboot
- Next by thread: [Discuss] systemd reboot
- Index(es):