----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
Xen-users@xxxxxxxxxxxxxxxxxxx <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>
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
------------------------------------------------------------------------
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
__________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 3317
(20080801) __________
E-Mail wurde geprüft mit ESET NOD32 Antivirus.
http://www.eset.com
