On Fri, Aug 1, 2008 at 9:16 AM, Alexander Hoßdorf
<xen-users@xxxxxxxxxxx> wrote:
You're right ;-)
But it won't kill him, to know how to mount LVM Partitions from DomU in Dom0.
Grant McWilliams schrieb:
----snip-----
Setting up Logical Volume Management: 2 logical volume(s) in
volume group "VolGroup00" now active
[ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VolGroup00/LogVol00
/dev/VolGroup00/LogVol00 contains a file system with errors, check
forced.
/dev/VolGroup00/LogVol00: Inode 67830 has illegal block(s).
/dev/VolGroup00/LogVol00: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
[FAILED]
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
----snip-----
So, how can I run fsck on that file system?
I have tried to mount /home/vm/vm01.img - but it fails:
# mount -o loop /home/vm/vm01.img /mnt/vm01/
mount: you must specify the filesystem type
--
Kind Regards
Rudi Ahlers
SoftDux CEO
_______________________________________________
Xen-users mailing list
http://lists.xensource.com/xen-users
Am I missing something? It seems like people like making things more complicated than they are. What's stopping you from doing an fsck from the console within the DomU just like if it were a real machine? It dropped you to a shell so just run fsck on it manually.
Grant McWilliams
------------------------------------------------------------------------
It's definitely better to learn something new but I also live by the idea that the simplest solution is the best.
It's quite strange that the DomU dies after throwing the error. Where does that fault lie? It seems like Xen should keep it running as if it were a real machine.
Grant McWilliams
