Last week, my wife rebooted our web server with the reset button (don't ask). It booted ok and appears to be running fine, but now I get this result from "fdisk -l" Disk /dev/hda: 80.0 GB, 80060424192 bytes 255 heads, 63 sectors/track, 9733 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 83 Linux /dev/hda2 14 26 104422+ 83 Linux /dev/hda3 27 39 104422+ 83 Linux /dev/hda4 40 9733 77867055 8e Linux LVM Disk /dev/dm-0: 8388 MB, 8388608000 bytes 255 heads, 63 sectors/track, 1019 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 8388 MB, 8388608000 bytes 255 heads, 63 sectors/track, 1019 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/dm-1 doesn't contain a valid partition table . . . . Disk /dev/dm-10: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/dm-10 doesn't contain a valid partition table Disk /dev/dm-11: 10.7 GB, 10737418240 bytes 255 heads, 63 sectors/track, 1305 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/dm-11 doesn't contain a valid partition table The /dev/dm-nn correspond to the 12 logical volumes in that VG. I checked dmesg and found this: EXT3-fs: dm-0: orphan cleanup on readonly fs ext3_orphan_cleanup: deleting unreferenced inode 1094899 ext3_orphan_cleanup: deleting unreferenced inode 227777 ext3_orphan_cleanup: deleting unreferenced inode 1078122 ext3_orphan_cleanup: deleting unreferenced inode 1466022 ext3_orphan_cleanup: deleting unreferenced inode 617737 ext3_orphan_cleanup: deleting unreferenced inode 617736 ext3_orphan_cleanup: deleting unreferenced inode 617735 ext3_orphan_cleanup: deleting unreferenced inode 617733 ext3_orphan_cleanup: deleting unreferenced inode 1239631 EXT3-fs: dm-0: 9 orphan inodes deleted EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. There's nothing in /lost+found. Several LVM tools I tried, including vgck report nothing amiss. vgscan, lvscan, vgdisplay all provide normal output. The system is FC4, updated nightly with yum. lvm RPM is lvm2-2.02.06-1.0.fc4. A Google search didn't turn up anything useful. As I noted, it's running fine, apparently, though, fdisk seems to expect partition tables in /dev/dm-nn. How do I fix this short of setting up a new drive and copying everything over? Cheers, -- Bob McClure, Jr. Bobcat Open Systems, Inc. bob@bobcatos.com http://www.bobcatos.com Blessed is the nation whose God is the LORD. - Psalm 33:12 Righteousness exalts a nation. - Proverbs 14:34 _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
