All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hari Kodungallur <hari.mailinglists@gmail.com>
To: xen-devel@lists.sourceforge.net
Subject: save/restore problems
Date: Tue, 29 Mar 2005 20:51:15 -0800	[thread overview]
Message-ID: <31d823d905032920513b25efa8@mail.gmail.com> (raw)

Hi All,

I am running into a bunch of problems when trying to do save/restore.
(I am NOT running the latest xen. I am running 2.0)

I am trying out the FC-1, and RH-ES-9 images. I can create domains for
all the three. But when I save some configurations of these images
(for example, install some rpms on a clean image and save the image)
and then restore them, I am running into the following issues:

(1) FC-1: The most success I have is with this. I can do save and
restore. But as soon as I execute a command remotely that modifies the
file system (e.g., "ssh -n hostname "do-some-fs-updates.sh"), it
starts complaining that the filesystem is read only. The error on the
console looks something like:

xen_blk:  Unexpected blkif status disconnected in state connected
blkfront: recovered 0 descriptors
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
EXT3-fs error (device sda1): ext3_free_blocks: bit already cleared for
block 293633
Aborting journal on device sda1.
ext3_abort called.
EXT3-fs error (device sda1): ext3_journal_start: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device sda1) in start_transaction: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device sda1) in
ext3_reserve_inode_write: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device sda1) in
ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sda1) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device sda1) in ext3_truncate: Journal has aborted
EXT3-fs error (device sda1) in start_transaction: Journal has aborted
EXT3-fs error (device sda1) in start_transaction: Journal has aborted


Doing this a couple of times (shutdown and then restore again)
corrupts the fs and then i need to run fsck at boot time to get back
to normal status.


(2) RH-ES-9: The save command ("xm save RHES9 myRHES9") just hangs.
Does not do anything.


My question is whether this is something that anyone have seen before
and/or whether anyone could point me to why this happens here and/or
whether installing 2.0.5 would solve this for me.

Thanks
-Hari


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30

             reply	other threads:[~2005-03-30  4:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30  4:51 Hari Kodungallur [this message]
     [not found] ` <1112289521.4997.59.camel@master.vms.security>
2005-03-31 19:46   ` Fwd: save/restore problems Hari Kodungallur
  -- strict thread matches above, loose matches on Subject: below --
2005-03-31 20:25 Ian Pratt

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=31d823d905032920513b25efa8@mail.gmail.com \
    --to=hari.mailinglists@gmail.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.