[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: domU oom -> xvda1 read-only without any notice?


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Ferenc Wagner <wferi@xxxxxxx>
  • Date: Thu, 01 Apr 2010 16:09:13 +0200
  • Delivery-date: Thu, 01 Apr 2010 07:09:52 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Ian Campbell <Ian.Campbell@xxxxxxxxxx> writes:

> On Wed, 2010-03-31 at 10:17 +0100, Josip Rodin wrote:
> Is it possible that this (which I presume is a flag set in the
> filesystem metadata):
>
>> [    9.996577] EXT3-fs warning (device xvda1): ext3_clear_journal_err: 
>> Filesystem error recorded from previous mount: IO failure
>> [    9.996585] EXT3-fs warning (device xvda1): ext3_clear_journal_err: 
>> Marking fs in need of filesystem check.
>
> would also have caused the filesystem to reject attempts to remount,rw
> before the reboot until you rebooted and fsck ran?
>
> I took a look at your logs (other mail) and I can't see any mention of
> an IO error on xvda either -- I must admit I'm pretty perplexed :-(

OTOH you shouldn't be surprised about not finding anything in the logs
about the filesystem being read-only. :)  Dmesg would have a bigger
chance of containing some traces, or network logs, if present.
-- 
Regards,
Feri.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.