FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 06-26-2008, 05:38 AM
"Nelson Strother"
 
Default where's the filesystem?

A Fedora9 system with the default layout of the / filesystem on LVM
was running, nearing the end of a packagekit update that was
installing six small bugfix updates. With no warning, the system
powered off. The electric supply was not interrupted, e.g. the UPS
did not chirp. Smartd has offered no complaints about the hard disk
drive. The filesystem was less than 60% full. Interesting.

On a few attempts to restart the system, running the same Fedora 9
system that spontaneously powered down, grub and boot sequence proceed
normally until just after the message "Starting udev" is displayed.
Then the system spontaneously powers down with no other message or
warning.

The system will successfully boot from a Fedora 9 system installed
on another partition, with a custom layout with the / filesystem in an
ext3 partition without LVM. Obviously, the first thing I would like
to do is to mount the / filesystem of the failing system, but attempts
to do so provide puzzling results. At the moment, the only LVM
visible to this system is the one containing the failing system. All
of the LVM queries seem to show it to be in good health, e.g.:

[root@localhost ~]# vgscan -v
Wiping cache of LVM-capable devices
Wiping internal VG cache
Reading all physical volumes. This may take a while...
Finding all volume groups
Finding volume group "VolGroupF9"
Found volume group "VolGroupF9" using metadata type lvm2
[root@localhost ~]# vgchange -ay
1 logical volume(s) in volume group "VolGroupF9" now active
[root@localhost ~]# lvscan
ACTIVE '/dev/VolGroupF9/LogVolF9' [5.66 GB] inherit
[root@localhost ~]# vgscan
Reading all physical volumes. This may take a while...
[root@localhost ~]# lvdisplay -v /dev/mapper/VolGroupF9
Using logical volume(s) on command line
--- Logical volume ---
LV Name /dev/VolGroupF9/LogVolF9
VG Name VolGroupF9
LV UUID aewqCH-Xna0-XRrY-KIVl-eBV2-oX50-9KK1XV
LV Write Access read/write
LV Status available
# open 0
LV Size 5.66 GB
Current LE 181
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

[root@localhost ~]# blkid /dev/sda1
:
/dev/mapper/VolGroupF9-LogVolF9: LABEL="Fedora-9-Live-i6"
UUID="0fda6f15-de41-4da6-8d7a-c1ee5385ea79" TYPE="ext3"
[root@localhost ~]#

But an attempt to mount this yields results which seem to imply the
filesystem is damaged.

[root@localhost ~]# mount -t ext3 /dev/mapper/VolGroupFedora9-LogVolF9
/mnt/F9root
mount: special device /dev/mapper/VolGroupFedora9-LogVolF9 does not exist
[root@localhost ~]# stat /dev/mapper/VolGroupFedora9-LogVolF9
stat: cannot stat `/dev/mapper/VolGroupFedora9-LogVolF9': No such file
or directory
[root@localhost ~]# stat -f /dev/mapper/VolGroupFedora9-LogVolF9
stat: cannot read file system information for
`/dev/mapper/VolGroupFedora9-LogVolF9': No such file or directory
[root@localhost ~]# cd /dev/mapper/
[root@localhost mapper]# pwd
/dev/mapper
[root@localhost mapper]# ls -al
total 0
drwxr-xr-x 2 root root 80 2008-06-25 00:44 .
drwxr-xr-x 14 root root 4360 2008-06-25 00:44 ..
crw-rw---- 1 root root 10, 60 2008-06-25 00:43 control
brw-rw---- 1 root disk 253, 0 2008-06-25 00:44 VolGroupF9-LogVolF9
[root@localhost mapper]# mount -vvv
/dev/mapper/VolGroupFedora9-LogVolF9 /mnt/F9root
mount: fstab path: "/etc/fstab"
mount: lock path: "/etc/mtab~"
mount: temp path: "/etc/mtab.tmp"
mount: no LABEL=, no UUID=, going to mount
/dev/mapper/VolGroupFedora9-LogVolF9 by path
mount: spec: "/dev/mapper/VolGroupFedora9-LogVolF9"
mount: node: "/mnt/F9root"
mount: types: "(null)"
mount: opts: "(null)"
mount: you didn't specify a filesystem type for
/dev/mapper/VolGroupFedora9-LogVolF9
I will try all types mentioned in /etc/filesystems or /proc/filesystems
mount: you must specify the filesystem type
[root@localhost mapper]# mount -t ext3 -vvv
/dev/mapper/VolGroupFedora9-LogVolF9 /mnt/F9root
mount: fstab path: "/etc/fstab"
mount: lock path: "/etc/mtab~"
mount: temp path: "/etc/mtab.tmp"
mount: no LABEL=, no UUID=, going to mount
/dev/mapper/VolGroupFedora9-LogVolF9 by path
mount: spec: "/dev/mapper/VolGroupFedora9-LogVolF9"
mount: node: "/mnt/F9root"
mount: types: "ext3"
mount: opts: "(null)"
mount: mount(2) syscall: source:
"/dev/mapper/VolGroupFedora9-LogVolF9", target: "/mnt/F9root",
filesystemtype: "ext3", mountflags: -1058209792, data: (null)
mount: special device /dev/mapper/VolGroupFedora9-LogVolF9 does not exist
[root@localhost mapper]#

Please remind me which queries could help explain or debug this
situation? Besides debugfs?

Cheers,
Nelson

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 06-26-2008, 07:08 AM
dexter
 
Default where's the filesystem?

On Thu June 26 2008 06:38:56 Nelson Strother wrote:
> [root@localhost ~]# stat -f /dev/mapper/VolGroupFedora9-LogVolF9
> stat: cannot read file system information for
> `/dev/mapper/VolGroupFedora9-LogVolF9': No such file or directory
> [root@localhost ~]# cd /dev/mapper/
> [root@localhost mapper]# pwd
> /dev/mapper
> [root@localhost mapper]# ls -al
> total 0
> drwxr-xr-x *2 root root * * *80 2008-06-25 00:44 .
> drwxr-xr-x 14 root root * *4360 2008-06-25 00:44 ..
> crw-rw---- *1 root root *10, 60 2008-06-25 00:43 control
> brw-rw---- *1 root disk 253, *0 2008-06-25 00:44 VolGroupF9-LogVolF9

VolGroupFedora9-LogVolF9 != VolGroupF9-LogVolF9
try stat -f /dev/mapper/VolGroupF9-LogVolF9


...dex



--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 
Old 06-26-2008, 11:46 AM
"Nelson Strother"
 
Default where's the filesystem?

On Thu, Jun 26, 2008 at 3:08 AM, dexter <dex.mbox@googlemail.com> 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@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
 

Thread Tools




All times are GMT. The time now is 02:54 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org