|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] [6388] Stop VM on ENOSPC error. |
Date: | Wed, 25 Feb 2009 13:29:40 -0600 |
User-agent: | Thunderbird 2.0.0.19 (X11/20090105) |
Jamie Lokier wrote:
Anthony Liguori wrote:This simply doesn't happen in practice. The FS needs to write data to the disk in order to remount it read-only. Once all writes start failing, the errors are cascading.The idea is that if the guest at least sees the I/O error, then it won't continue writing as if everything were OK. It may not be able to continue normal operation, but it can at least mark the FS read-only and avoid ongoing damage.ext2/3/4 have documented errors=remount-ro / errors=panic mount options. Don't they work?
This was a sles10sp1 guest which uses reiserfs by default. Regards, Anthony Liguori
[Prev in Thread] | Current Thread | [Next in Thread] |