Hey everyone, Thanks for the quick help resonses once again, We got some mail saying that RAM disks were not the way to go. So we re-installed, made several partitions to use, and rebuilt xen. However, we''re still having trouble mounting partitions when xeno-linux boots. We give a physical grant of one of our newly made paritions (/dev/hda14 in particular) to the domain. But when we start a xenlinux domain we get error messages saying that "Your systems appears to have shut down uncleanly". It then proceeds to check the root file system and runs fsck on it, which goes fine. It tries to activate swap but it can''t seem to find /dev/hda3. These seem odd but not critical. Then it tries to do fsck on /dev/hda1 (boot) and we get a error message saying "The superblock could not be read or does not describe a correct ext2 filesystem". It does this for all filesystems in the fstab file. For the one we give a physical grant (/dev/hda14, mounted on /xen1), it goes into a seemingly infinate loop where we see the message "/xen1: recovering journal" over and over unitl it runs out of file descriptors. As usual we''ll take any suggestions. We think we might need to unmount the filesystems from the domain0 before letting other Xenolinuxes get a hold of them, but that doesn''t explain where our other errors come from. Attached is the log, in case that helps any. More thanks, David Berlin, Jeremy Chiu, Jefferson Ng --- This is part of the xenolinux startup log The lines with "**" in front are the ones we think are important [2] Welcome to Red Hat Linux [2] Press ''I'' to enter interactive startup. [2] Mounting proc filesystem: [ OK ] [2] Configuring kernel parameters: [ OK ] [2] modprobe: modprobe: Can''t open dependencies file /lib/modules/2.4.22-xeno/modules.dep (No such file or directory) [2] modprobe: modprobe: Can''t open dependencies file /lib/modules/2.4.22-xeno/modules.dep (No such file or directory) [2] hwclock is unable to get I/O port access: the iopl(3) call failed. [2] Setting clock (localtime): Sat Dec 6 14:16:51 PST 2003 [ OK ] [2] Setting hostname localhost.localdomain: [ OK ] [2] modprobe: Can''t open dependencies file /lib/modules/2.4.22-xeno/modules.dep (No such file or directory) **[2] Your system appears to have shut down uncleanly [2] Press Y within 5 seconds to force file system integrity check... Press Y within 4 seconds to force file system integrity check... Press Y within 3 seconds to force file system integrity check... Press Y with [2] k... Press Y within 1 seconds to force file system integrity check... [2] Checking root filesystem [2] /: clean, 131153/2052288 files, 715068/4096575 blocks [2] [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/hda2 [2] [ OK ] [2] Remounting root filesystem in read-write mode: [ OK ] **[2] Activating swap partitions: swapon: /dev/hda3: No such device [2] [FAILED] [2] Finding module dependencies: depmod: Can''t open /lib/modules/2.4.22-xeno/modules.dep for writing [2] [FAILED] [2] Checking filesystems **[2] fsck.ext3/dev/hda1: **[2] The superblock could not be read or does not describe a correct ext2 **[2] filesystem. If the device is valid and it really contains an ext2 **[2] filesystem (and not swap or ufs or something else), then the superblock **[2] is corrupt, and you might try running e2fsck with an alternate superblock: [2] e2fsck -b 8193 <device> [2] **[2] : Invalid argument while trying to open /dev/hda1 **[2] /xen1: recovering journal [2] /xen1: recovering journal [2] /xen1: recovering journal [2] /xen1: recovering journal [2] /xen1: recovering journal [2] /xen1: recovering journal . . . ------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> We got some mail saying that RAM disks were not the way to go. So we > re-installed, made several partitions to use, and rebuilt xen. However, > we''re still having trouble mounting partitions when xeno-linux boots. > > We give a physical grant of one of our newly made paritions (/dev/hda14 in > particular) to the domain. But when we start a xenlinux domain we get > error messages saying that "Your systems appears to have shut down > uncleanly". It then proceeds to check the root file system and runs fsck > on it, which goes fine. It tries to activate swap but it can''t seem to > find /dev/hda3. These seem odd but not critical.You need to allocate a swap partition per domain, and grant each domain physical access to its particular swap partition. The alternative is simply not to configure the guest OS to use swap -- we commonly operate in this mode with no problems. Once we have reimplemented ''virtual disc'' support over our new unstable toolset, it will then be possible to very easily allocate a ''virtual swap device'' to new guest OSes without any need to repartition your hard disc or worry about limitations on the number of partitions supported by a disc. This is still work in progress, however.> Then it tries to do fsck on /dev/hda1 (boot) and we get a error message > saying "The superblock could not be read or does not describe a correct > ext2 filesystem". It does this for all filesystems in the fstab file. > For the one we give a physical grant (/dev/hda14, mounted on /xen1), it > goes into a seemingly infinate loop where we see the message "/xen1: > recovering journal" over and over unitl it runs out of file descriptors. > > As usual we''ll take any suggestions. We think we might need to unmount > the filesystems from the domain0 before letting other Xenolinuxes get a > hold of them, but that doesn''t explain where our other errors come from.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. -- Keir ------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> 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)I presume you''ve written a script for domain 1 that does a ''physical grant -phda14 -w'' ? It looks like part of the problem is that you don''t have write access to the partition. If you still have problems, please can you tell us a bit more about your exact file system configuration, your xenctl.xml file, the scripts you''ve written to start each domain, etc. It''s odd that you''re having so much trouble as at least as far as I can figure from previous emails you''re not trying to setup a configuration that''s at all unusual. I''m sure we can get this figured out... Ian ------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel