> The only filesystem that both DOM0 and the new domain should
> simultaneously have mounted is /usr, which they should both have mounted
> read-only. Any other configuration (e.g., DOM0 still having hda14
> mounted) is rather unlikely to work as both OSes will fight over the
> superblock.
Ah.
Alright, we've unmounted the other devices from domain0, but we still get
the same problem: "superblock cannot be read or does not describe an ext2
filesystem". The filesystems are ext3, but as far as we can tell ext3 is
in every way compatible with ext2.
For /xen1(/dev/hda14), or the partition which we give a physical grant, we
get the following errors:
/xen1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY
(i.e. without -a or -p options)
/xen1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY
(i.e. without -a or -p options)
/xen1:clean, 11/26104 files, 7429/104391 blocks
Error writing block 269, (Attempt to write block from filesystem resulted
in short write) Error writing block 269, (Attempt to write block from
filesystem resulted in short write)
We're really unsure why it keeps thinking the filesystem isn't readable or
corrupted. Even weirder, sometimes when we start up domain0 it complains
that the drives aren't clean and need to be fscked as well. But we reboot
redHat the right way(log out, reboot), and we destroy all of the domains
we've tried before restarting.
Are there any termination procedures we should be aware of, and any tips
on why it doesn't like our partitions?
Apologies for persistence,
-Jefferson
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home