On Thu, Jun 26, 2008 at 3:08 AM, dexter <dex.mbox@xxxxxxxxxxxxxx> wrote:
> VolGroupFedora9-LogVolF9 != VolGroupF9-LogVolF9
> try stat -f /dev/mapper/VolGroupF9-LogVolF9
Thank you for the careful reading. Yes, spelled correctly, the LVM
can be mounted (wiping egg off face):
[root@localhost mapper]# stat -f /dev/mapper/VolGroupF9-LogVolF9
File: "/dev/mapper/VolGroupF9-LogVolF9"
ID: 0 Namelen: 255 Type: tmpfs
Block size: 4096 Fundamental block size: 4096
Blocks: Total: 64379 Free: 64353 Available: 64353
Inodes: Total: 64379 Free: 63374
[root@localhost mapper]# mount -t ext3 /dev/mapper/VolGroupF9-LogVolF9
/mnt/F9root
[root@localhost mapper]#
Even though the Free block count seems too large for a filesystem
that is 55% full, data is still accessible. Nothing exciting was
written to /var/log/messages on the way down, and nothing was flushed
out of buffers to log anything from the failed boot attempts.
/var/log/yum.log shows 4 (of the 6) updates completed:
Jun 21 11:43:45 Updated: gnome-python2-canvas-2.22.1-2.fc9.i386
Jun 24 06:53:51 Updated: compiz-0.7.6-2.fc9.i386
Jun 24 06:54:15 Installed: compiz-fusion-0.7.6-1.fc9.i386
Jun 24 06:54:42 Updated: 1:NetworkManager-openvpn-0.7.0-13.svn3632.fc9.i386
Jun 24 06:54:47 Updated: gnome-python2-extras-2.19.1-16.fc9.i386
/var/log/messages ends with:
Jun 24 06:53:52 localhost yum: Updated: compiz-0.7.6-2.fc9.i386
Jun 24 06:54:15 localhost yum: Installed: compiz-fusion-0.7.6-1.fc9.i386
Jun 24 06:54:42 localhost yum: Updated:
1:NetworkManager-openvpn-0.7.0-13.svn3632.fc9.i386
Jun 24 06:54:47 localhost yum: Updated: gnome-python2-extras-2.19.1-16.fc9.i386
Jun 24 06:57:13 localhost gconfd (u-28556): Exiting
Guess I will try booting without "quiet", etc. to attempt to learn more.
Cheers,
Nelson
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
