Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
SLES.11.3 ext3 filesystem error after multiple shutdowns
Version-Release number of selected component (if applicable):
Host: qemu-kvm-1.5.3-7.el7.x86_64
kernel-3.10.0-23.el7.x86_64
Guest: SLES.11.3 GA
How reproducible:
twice
Steps to Reproduce:
1.install a SLES.11.3 VM
2.run a bunch of tests(using kvm-autotest, function_base test loop)
including vm install/reboot/shutdown/system_reset/format_disk
file transfer/ping/etc
/root/staf-kvm-devel/autotest-devel/client/tests/virt/qemu/qemu \
-S \
-name 'virt-tests-vm1' \
-nodefaults \
-chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20130929-003315-3uTocRrg,server,nowait \
-mon chardev=qmp_id_qmpmonitor1,mode=control \
-chardev socket,id=serial_id_serial1,path=/tmp/serial-serial1-20130929-003315-3uTocRrg,server,nowait \
-device isa-serial,chardev=serial_id_serial1 \
-chardev socket,id=seabioslog_id_20130929-003315-3uTocRrg,path=/tmp/seabios-20130929-003315-3uTocRrg,server,nowait \
-device isa-debugcon,chardev=seabioslog_id_20130929-003315-3uTocRrg,iobase=0x402 \
-device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=0x4 \
-drive file='/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/sles11sp3-64-virtio.qcow2',index=0,if=none,id=drive-virtio-disk1,media=disk,cache=none,snapshot=off,format=qcow2,aio=native \
-device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,bootindex=0 \
-device virtio-net-pci,netdev=idzbD86f,mac='9a:59:5a:5b:5c:5d',bus=pci.0,addr=0x3,id='idVTbd3f' \
-netdev tap,id=idzbD86f,vhost=on,vhostfd=26,fd=25 \
-m 4096 \
-smp 1,maxcpus=1,cores=1,threads=1,sockets=2 \
-cpu 'Opteron_G2' \
-M pc \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-spice port=3000,password=123456,addr=0,image-compression=auto_glz,zlib-glz-wan-compression=auto,streaming-video=all,agent-mouse=on,playback-compression=on,ipv4 \
-vga qxl \
-global qxl-vga.vram_size=33554432 \
-rtc base=utc,clock=host,driftfix=slew \
-boot order=cdn,once=c,menu=off \
-no-kvm-pit-reinjection \
-enable-kvm
3.
Actual results:
VM ext3 fs error when boot after bug occurs, and ask to type in root passwd to enter fix mode
Expected results:
both vm and host work well
Additional info:
after type in root password, and exec 'fsck.ext3 -y /dev/vda2', and reboot
guest fs work fine.
hi, Hai Huang:
I met the similar bugs some weeks ago. My system environment is:
HOST:
suse 10, the kernel version is 2.6.32.43
Qemu-KVM 1.2
Libvirt 1.0
guest OS:
suse 10, the kernel version is 2.6.32.43
VM use a qcow2 disk.
Description of problem:
I have 20 VMs with qcow2 disk, I have shutdown these VMs many times by "virsh destroy" during VM installation.
When these vm reboot,dmesg show a ext3-fs mount error occurred on partion /dev/vda3:
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
and when I wrote into partion /dev/vda3,some errors occurred in dmesg:
1.error (device vda3): ext3_free_blocks: Freeing blocks not in datazone - block = 1869619311, count = 1
error (device vda3): ext3_free_blocks_sb: bit already cleared for block 2178152
error (device vda3): ext3_readdir: bad entry in directory #1083501:
2.[347470.661893] attempt to access beyond end of device
[347470.661896] vda3: rw=0, want=6870892952, limit=41945715
[347470.661897] EXT3-fs error (device vda3): ext3_free_branches: Read failure, inode=1083508, block=858861618
3.EXT3-fs error (device vda3): ext3_new_block: block(4295028581) >= blocks count(-1) - block_group = 1, es == ffff88021b6c7400
I can't reproduce this bug now. I suspect this fs-error is caused by multiple forced shutdown, but I am not sure.
Do you have some breakthrough about this bug?
Description of problem: SLES.11.3 ext3 filesystem error after multiple shutdowns Version-Release number of selected component (if applicable): Host: qemu-kvm-1.5.3-7.el7.x86_64 kernel-3.10.0-23.el7.x86_64 Guest: SLES.11.3 GA How reproducible: twice Steps to Reproduce: 1.install a SLES.11.3 VM 2.run a bunch of tests(using kvm-autotest, function_base test loop) including vm install/reboot/shutdown/system_reset/format_disk file transfer/ping/etc /root/staf-kvm-devel/autotest-devel/client/tests/virt/qemu/qemu \ -S \ -name 'virt-tests-vm1' \ -nodefaults \ -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20130929-003315-3uTocRrg,server,nowait \ -mon chardev=qmp_id_qmpmonitor1,mode=control \ -chardev socket,id=serial_id_serial1,path=/tmp/serial-serial1-20130929-003315-3uTocRrg,server,nowait \ -device isa-serial,chardev=serial_id_serial1 \ -chardev socket,id=seabioslog_id_20130929-003315-3uTocRrg,path=/tmp/seabios-20130929-003315-3uTocRrg,server,nowait \ -device isa-debugcon,chardev=seabioslog_id_20130929-003315-3uTocRrg,iobase=0x402 \ -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=0x4 \ -drive file='/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/sles11sp3-64-virtio.qcow2',index=0,if=none,id=drive-virtio-disk1,media=disk,cache=none,snapshot=off,format=qcow2,aio=native \ -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,bootindex=0 \ -device virtio-net-pci,netdev=idzbD86f,mac='9a:59:5a:5b:5c:5d',bus=pci.0,addr=0x3,id='idVTbd3f' \ -netdev tap,id=idzbD86f,vhost=on,vhostfd=26,fd=25 \ -m 4096 \ -smp 1,maxcpus=1,cores=1,threads=1,sockets=2 \ -cpu 'Opteron_G2' \ -M pc \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -spice port=3000,password=123456,addr=0,image-compression=auto_glz,zlib-glz-wan-compression=auto,streaming-video=all,agent-mouse=on,playback-compression=on,ipv4 \ -vga qxl \ -global qxl-vga.vram_size=33554432 \ -rtc base=utc,clock=host,driftfix=slew \ -boot order=cdn,once=c,menu=off \ -no-kvm-pit-reinjection \ -enable-kvm 3. Actual results: VM ext3 fs error when boot after bug occurs, and ask to type in root passwd to enter fix mode Expected results: both vm and host work well Additional info: after type in root password, and exec 'fsck.ext3 -y /dev/vda2', and reboot guest fs work fine.