Bug 160444
| Summary: | mkrootdev: label / not found with / in xfs - Kernel panic | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Laurent Blin <laurent_blin> |
| Component: | grub | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | CC: | axel.thimm, gbritton, joe, orion |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-07-06 22:21:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Laurent Blin
2005-06-15 07:49:39 UTC
Here are the complete messages: root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LQBEL=/ rhgb quiet [Linux-bzImage, setup=0x1e00, size=0x18e473] initrd /initrd-2.6.11-1.1369_FC4.img [Linux-initrd @ 0xfe22000,0x13ddde bytes] Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 4.2.15 starting mkrootdev: label / not found mount: error 2 mounting xfs ERROR opeing /dev/console!!!!: 2 error dup2'ing fd of 0 to 0 error dup2'ing fd of 0 to 1 error dup2'ing fd of 0 to 2 switchroot: mount failed: 22 Kernel panic - not syncing: Attempted to kill init! No pb when I use an EXT3 formatted / partition, and keep a XFS /home. Is there a pb loading a / in XFS? I can confirm this bug report. Just did "linux xfs" install with manually created partitions. Had to use Kubuntu livecd (the only one handy) to xfs_admin -L / /dev/sda3 (my root partition) to fix it. The installer doesn't label the XFS root partition for some reason at all. I ran into this issue and the fix initially worked, but I ended up with grub losing one of its stages and booting to just "GRUB " so I booted in rescue mode prepared to do a grub-install to fix it, but that would segfault within grub. After installing grub-debuginfo, I found that it was in xfs traversal code that grub was segfaulting. My guess is that grub-install won't work properly on a mounted xfs filesystem (and since grub requires writing to the filesystem, this may not be easily solvable). I reinstalled with an ext3 /boot, and went over to a shell at the end of the installation process to relabel the / filesystem, and looked at what it was labeled initially and found that it had been labeled properly with "/" as the filesystem label, however, the filesystem was inconsistant with the duplicate superblocks (or xfs's equivalent) not agreeing. I suspect anaconda may have labeled the filesystem while it was mounted (which xfs does not seem to safely support). This bug probably ought to be an anaconda bug. Looks like the initial label created during install is bad somehow: [root@coop01 ~]# mount -a mount: special device LABEL=/scratch does not exist [root@coop01 ~]# xfs_admin -l -f /dev/hda7 warning: AG 1 label differs warning: AG 2 label differs warning: AG 3 label differs warning: AG 4 label differs warning: AG 5 label differs warning: AG 6 label differs warning: AG 7 label differs warning: AG 8 label differs warning: AG 9 label differs warning: AG 10 label differs warning: AG 11 label differs warning: AG 12 label differs warning: AG 13 label differs warning: AG 14 label differs warning: AG 15 label differs label = "/scratch" [root@coop01 ~]# xfs_admin -L /scratch -f /dev/hda7 writing all SBs new label = "/scratch" [root@coop01 ~]# xfs_admin -l -f /dev/hda7 label = "/scratch" [root@coop01 ~]# mount /scratch [root@coop01 ~]# Check if this relates to the bug that I had here with a deficient initial root disk image, Bug # 161406 xfs is completely unsupported. |