Description of problem:
After the recent upgrade my Fedora 8 image could no longer boot.
Version-Release number of selected component (if applicable):
kvm-60-2.fc8.x86_64 (broken)
kvm-60-1.fc8.x86_64 (OK)
How reproducible:
Tried once. (I no longer have the appropriate image now.)
Steps to Reproduce:
1. Install F8 GA into kvm-60-1.fc8.
2. `yum update kernel' in this F8 GA.
3. Shutdown kvm.
4. Upgrade kvm to: kvm-60-2.fc8
5. Start kvm.
Actual results:
/1 primary superblock features different from backup, check forced.
Restarting system.
---> KVM restart
/1 primary superblock features different from backup, check forced.
Restarting system.
---> ad infinitum
Expected results:
/1 primary superblock features different from backup, check forced.
Restarting system.
---> KVM restart
/1: clean, ...
Additional info:
Downgrade to kvm-60-1.fc8.x86_64 really fixed the problem.
Expecting an off-by-one bug in the fix of the Bug 433560:
* Sat Feb 23 2008 Daniel P. Berrange <email address hidden> - 60-2.fc8
- Fix block device extents check (rhbz #433560)
The message:
/1 primary superblock features different from backup, check forced.
is right as it happened during the recent F8 kernel update.
But it should happen only once.
Expecting some ext3 superblock backup near the end of the media got ignored.
Used disk image layout:
The partition is aligned to the physical end of the media but it does not exceed it!
in KVM:
/dev/sda:
geometry = 509/255/63, sectors = 8192000, start = 0
Disk /dev/sda: 4194 MB, 4194304000 bytes
255 heads, 63 sectors/track, 509 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000d71ca
Device Boot Start End Blocks Id System
/dev/sda1 * 1 509 4088511 83 Linux
Disk /dev/sda: 255 heads, 63 sectors, 509 cylinders
Description of problem:
After the recent upgrade my Fedora 8 image could no longer boot.
Version-Release number of selected component (if applicable):
kvm-60-2.fc8.x86_64 (broken)
kvm-60-1.fc8.x86_64 (OK)
How reproducible:
Tried once. (I no longer have the appropriate image now.)
Steps to Reproduce:
1. Install F8 GA into kvm-60-1.fc8.
2. `yum update kernel' in this F8 GA.
3. Shutdown kvm.
4. Upgrade kvm to: kvm-60-2.fc8
5. Start kvm.
Actual results:
/1 primary superblock features different from backup, check forced.
Restarting system.
---> KVM restart
/1 primary superblock features different from backup, check forced.
Restarting system.
---> ad infinitum
Expected results:
/1 primary superblock features different from backup, check forced.
Restarting system.
---> KVM restart
/1: clean, ...
Additional info:
Downgrade to kvm-60-1.fc8.x86_64 really fixed the problem.
Expecting an off-by-one bug in the fix of the Bug 433560:
* Sat Feb 23 2008 Daniel P. Berrange <email address hidden> - 60-2.fc8
- Fix block device extents check (rhbz #433560)
The message:
/1 primary superblock features different from backup, check forced.
is right as it happened during the recent F8 kernel update.
But it should happen only once.
Expecting some ext3 superblock backup near the end of the media got ignored.
Used disk image layout:
The partition is aligned to the physical end of the media but it does not exceed it!
in KVM:
/dev/sda:
geometry = 509/255/63, sectors = 8192000, start = 0
Disk /dev/sda: 4194 MB, 4194304000 bytes
255 heads, 63 sectors/track, 509 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000d71ca
Device Boot Start End Blocks Id System
/dev/sda1 * 1 509 4088511 83 Linux
Disk /dev/sda: 255 heads, 63 sectors, 509 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 1 1 0 254 63 508 63 8177022 83
2 00 0 0 0 0 0 0 0 0 00
3 00 0 0 0 0 0 0 0 0 00
4 00 0 0 0 0 0 0 0 0 00
qemu-img:
file format: qcow2
virtual size: 3.9G (4194304000 bytes)
Expecting this Bug should get cloned across all the Fs/RHELs and for QEMU.