jaapengel79
MIS
Hi,
One of our SuSE Linux Enterprise 10 64-bit servers was rebooted yesterday afternoon after some application issues which couldn't be resolved otherwise.
As the machine rebooted, it went into maintenance mode because of some filesystem issues. After some reiserfsck'ing (which resulted in 'No inconsistencies found' for everything we tried), we booted through an installation DVD to Repair the System. There was one file system that indicated a 'block device not found' (or 'invalid block device', something along those lines). Through the Repair System function of the DVD we accessed /etc/fstab on the root LV and remarked that filesystem. After a reboot, the system came up perfectly well.
To make a long story short, lvdisplay indicated the conflicting filesystem was pointing to "253,7". However, an ls -l /dev/mapper/system-LV--etcapachelog (the faulty filesystem) showed it was linked to 253,10 ... which did indeed not exist. It was fixed by renaming the system-LV--etcapachelog, and creating a new one using 'mknod' ..
Here's my question: what could lead to a mismatch between what lvdisplay 'sees' and what /dev/mapper/system-LV--etcapachelog says it's linked to??
One of our SuSE Linux Enterprise 10 64-bit servers was rebooted yesterday afternoon after some application issues which couldn't be resolved otherwise.
As the machine rebooted, it went into maintenance mode because of some filesystem issues. After some reiserfsck'ing (which resulted in 'No inconsistencies found' for everything we tried), we booted through an installation DVD to Repair the System. There was one file system that indicated a 'block device not found' (or 'invalid block device', something along those lines). Through the Repair System function of the DVD we accessed /etc/fstab on the root LV and remarked that filesystem. After a reboot, the system came up perfectly well.
To make a long story short, lvdisplay indicated the conflicting filesystem was pointing to "253,7". However, an ls -l /dev/mapper/system-LV--etcapachelog (the faulty filesystem) showed it was linked to 253,10 ... which did indeed not exist. It was fixed by renaming the system-LV--etcapachelog, and creating a new one using 'mknod' ..
Here's my question: what could lead to a mismatch between what lvdisplay 'sees' and what /dev/mapper/system-LV--etcapachelog says it's linked to??